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 vstinner
Recipients belopolsky, tim.peters, vstinner
Date 2014-08-01.00:44:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Oh, I forgot to mention that the patch of the issue #22043 also changes _PyTimeSpec_get_time() to use clock_gettime(CLOCK_REALTIME) which has a resolution of 1 nanosecond.

_PyTimeSpec_get_time() already uses GetSystemTimeAsFileTime() which has a resolution of 100 nanosecond. See also the issue #19007 "precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime".

I'm talking about the resolution of the C structure. The effive resolution can be much worse than that. For example, the resolution measured in Python of clock_gettime(CLOCK_REALTIME) is closer to 160 nanoseconds (on my laptop) than 1 nanoescond. See the "Python Resolution" column the second table of:
Date User Action Args
2014-08-01 00:44:08vstinnersetrecipients: + vstinner, tim.peters, belopolsky
2014-08-01 00:44:08vstinnersetmessageid: <>
2014-08-01 00:44:08vstinnerlinkissue22117 messages
2014-08-01 00:44:08vstinnercreate