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 trent
Recipients Arfrever, larry, pitrou, skrah, trent
Date 2012-10-17.10:05:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Here's a thought...  why not alter the test to work with fixed times and separate the atime tests from the mtime tests.

For atime, we can set utime(filename, (0.0, ...)) and see if a subsequent os.stat() returns st_atime as 0.0 -- that'll tell us whether or not atime is affected.

For the mtime tests, rather than having a variable UTIME_EPSILON, just have fixed dates that match the expected precision of the underlying platform?
Date User Action Args
2012-10-17 10:05:21trentsetrecipients: + trent, pitrou, larry, Arfrever, skrah
2012-10-17 10:05:21trentsetmessageid: <>
2012-10-17 10:05:21trentlinkissue15745 messages
2012-10-17 10:05:21trentcreate