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 jsjgruber
Recipients alexis, eric.araujo, jsjgruber, tarek
Date 2011-05-04.02:23:47
SpamBayes Score 1.5173552e-09
Marked as misclassified No
Message-id <1304475832.41.0.871788475686.issue11993@psf.upfronthosting.co.za>
In-reply-to
Content
This report is meant to prompt discussion, if desired, on the advisability of distinguishing new files from old using subsecond data. (It isn't clear to me that it is important to do this.)

Some file systems keep sub-second modification times, but the number of seconds since the epoch grows to a very large number, and given the limited number of significant bits in floating point numbers, it's important to carry out this comparison carefully (or use some new integer data) so newly created files don't appear to be older than their source files due to rounding and other conversion anomalies. Current floats don't have the precision to hold both the number of seconds since the epoch and a nanosecond precision fractional second.
History
Date User Action Args
2011-05-04 02:23:52jsjgrubersetrecipients: + jsjgruber, tarek, eric.araujo, alexis
2011-05-04 02:23:52jsjgrubersetmessageid: <1304475832.41.0.871788475686.issue11993@psf.upfronthosting.co.za>
2011-05-04 02:23:47jsjgruberlinkissue11993 messages
2011-05-04 02:23:47jsjgrubercreate