Message 173151 - Python tracker

➜

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	<1350468321.81.0.661050926246.issue15745@psf.upfronthosting.co.za>
In-reply-to

Content
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?

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?

History
Date	User	Action	Args
2012-10-17 10:05:21	trent	set	recipients: + trent, pitrou, larry, Arfrever, skrah
2012-10-17 10:05:21	trent	set	messageid: <1350468321.81.0.661050926246.issue15745@psf.upfronthosting.co.za>
2012-10-17 10:05:21	trent	link	issue15745 messages
2012-10-17 10:05:21	trent	create