Daniel Eriksson added the comment: @Larry
The issue is the following: In the test after the first p.touch (Pdb) old_mtime 1407128672.4133856 (Pdb) old_mtime_ns 1407128672413385711 After second p.touch (Pdb) st.st_mtime_ns 1407128689000000000 (Pdb) st.st_mtime 1407128689.0 So the issue is that when utime is used it can't set the time with nanosecond, but just with second resolution. @Francis - A quick fix that would work, but it is a bit dirty but it will work correctly is to just add two p.touch() before doing anything. Not really the best solution but could work. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue19838> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
