➜

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 steve.dower
Recipients brian.curtin, jkloth, loewis, pitrou, python-dev, steve.dower, tim.golden, tim.peters
Date 2013-11-22.23:02:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385161380.04.0.173384544069.issue19715@psf.upfronthosting.co.za>
In-reply-to
Content 
I don't have any extra insight into this. The documented resolution for mtime on NTFS is 100ns (2s on FAT32), so without delaying by at least that long you're not going to see an official change. The noise is probably from floating-point conversions (in _PyTime_ObjectToDenominator, at a guess).

Maybe you want to test to be a bit more generous with the bounds:

1. touch
2. get original_mtime
3. utime(10s ago)
4. verify p.stat().st_mtime < original_mtime
5. store old_mtime
6. touch
7. verify p.stat().st_mtime > old_mtime
OR
7. verify original_mtime - 0.001 < p.stat().st_mtime < original_mtime + 0.001
History
Date User Action Args
2013-11-22 23:03:00steve.dowersetrecipients: + steve.dower, tim.peters, loewis, pitrou, tim.golden, jkloth, brian.curtin, python-dev
2013-11-22 23:03:00steve.dowersetmessageid: <1385161380.04.0.173384544069.issue19715@psf.upfronthosting.co.za>
2013-11-22 23:03:00steve.dowerlinkissue19715 messages
2013-11-22 23:02:59steve.dowercreate