Martin v. Löwis added the comment:
>> Then, the utime call in step 4 asked to set this to
> You mean step 3, right? ("date back 10s")
No, I really meant step 4 (touch). The second touch call *really* steps
backwards. I don't find that very surprising, since it is actually the first
call that passes an actual time.
I can readily believe that Windows uses different rounding algorithm when
creating a fresh file than Python uses when converting a float to a FILETIME.
> (note also how far 1385154213 is from 1303049222, but the test is
> careful to avoid that)
These are really entirely different values. 1385154213 is the number of seconds
since 1970. 1303049222 is the dwLowDateTime of that timestamp, i.e. the lower
32-bit in units of 100 ns since 1601.
This test *does* fail because of a few nanoseconds - I don't understand why you
claim that it cannot.
----------
_______________________________________
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
