homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Arfrever
Recipients Alexander.Belopolsky, Arfrever, belopolsky, ericography, jcea, khenriksson, larry, lars.gustaebel, loewis, mark.dickinson, nadeem.vawda, r.david.murray, rhettinger, rosslagerwall, skrah, vstinner
Date 2012年01月30日.14:20:57
SpamBayes Score 0.13346191
Marked as misclassified No
Message-id <1327933258.01.0.0057281920586.issue11457@psf.upfronthosting.co.za>
In-reply-to
Content
(secs, nsecs) tuples are more practical in performance-critical applications (e.g. synchronization of timestamps between 2 trees with large number of files).
History
Date User Action Args
2012年01月30日 14:20:58Arfreversetrecipients: + Arfrever, loewis, rhettinger, jcea, mark.dickinson, belopolsky, lars.gustaebel, vstinner, larry, nadeem.vawda, r.david.murray, skrah, Alexander.Belopolsky, rosslagerwall, khenriksson, ericography
2012年01月30日 14:20:58Arfreversetmessageid: <1327933258.01.0.0057281920586.issue11457@psf.upfronthosting.co.za>
2012年01月30日 14:20:57Arfreverlinkissue11457 messages
2012年01月30日 14:20:57Arfrevercreate

AltStyle によって変換されたページ (->オリジナル) /