Steve Dower added the comment: 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 ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19715> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
