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 loewis
Recipients brian.curtin, jkloth, loewis, pitrou, python-dev, steve.dower, tim.golden, tim.peters
Date 2013-11-23.00:42:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385167340.97.0.179366247244.issue19715@psf.upfronthosting.co.za>
In-reply-to
Content
Looking at the ReactOS sources, it appears that Windows doesn't do any rounding, so it's all Python's fault. Windows keeps its system time (in KI_USER_SHARED_DATA) in essentially a FILETIME represenation (i.e. units of 100ns since 1601), and never needs to convert it. So CreateFile just uses the current system time as-is when filling the LastWriteTime.

I don't think it's enough for Python to convert these monotonically. The error would already occur if Python cannot convert bijectively, i.e. if getting the system time into float and back won't get the same FILETIME. It might just be that a 64-bit float value (with 53 bit mantissa) is too imprecise for that operation. A FILETIME currently has 56 significant bits.
History
Date User Action Args
2013-11-23 00:42:21loewissetrecipients: + loewis, tim.peters, pitrou, tim.golden, jkloth, brian.curtin, python-dev, steve.dower
2013-11-23 00:42:20loewissetmessageid: <1385167340.97.0.179366247244.issue19715@psf.upfronthosting.co.za>
2013-11-23 00:42:20loewislinkissue19715 messages
2013-11-23 00:42:20loewiscreate