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 Arfrever, Niklas.Claesson, Ramchandra Apte, andrewclegg, belopolsky, ethan.furman, goshawk, lemburg,, pitrou, pythonhacker, r.david.murray, scoobydoo, serhiy.storchaka, tim.peters, vstinner
Date 2015-04-09.22:07:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> My patch for the issue #22043 adds nanosecond precision to get the system clock.

In fact, nanosecond resolution was added by the issue #22117. In Python 3.5, calls _PyTime_GetSystemClock() which has now a resolution of 1 nanosecond.

The C type has a resolution of 1 nanosecond, the effictive resolution depends on the platform. For example, Windows provides GetSystemTimeAsFileTime() which has a resolution of 100 ns (and the effective accuracy is closer to 15 ms: see issue #13845).
Date User Action Args
2015-04-09 22:07:24vstinnersetrecipients: + vstinner, lemburg, tim.peters, belopolsky, pitrou, pythonhacker, Arfrever, r.david.murray, andrewclegg, ethan.furman, Ramchandra Apte, serhiy.storchaka, goshawk, Niklas.Claesson,, scoobydoo
2015-04-09 22:07:24vstinnersetmessageid: <>
2015-04-09 22:07:24vstinnerlinkissue15443 messages
2015-04-09 22:07:24vstinnercreate