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 akira, belopolsky, lemburg, pitrou, steve.dower, tim.golden, tim.peters, vstinner, zach.ware
Date 2015-07-31.22:05:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Note: GetSystemTimePreciseAsFileTime() is restricted to desktop applications.

The has a warning on this function:

"""  Desktop Applications: GetSystemTimePreciseAsFileTime()

The function shall also be used with care when a system time adjustment is active. Current Windows versions treat the performance counter frequency as a constant. The high resolution of GetSystemTimePreciseAsFileTime() is derived from the performance counter value at the time of the call and the performance counter frequency. However, the performance counter frequency should be corrected during system time adjustments to adapt to the modified progress in time. Current Windows versions don't do this. The obtained microsecond part may be severely affected when system time adjustments are active. Seconds may consist of more or less than 1.000.000 microseconds. Microsoft may or not fix this in one of the next updates/versions.
As of May, 2015 the inaccuracy of GetSystemTimePreciseAsFileTime() during system time adjustments persists for the preview versions of Windows 10.

Is it ok to switch to GetSystemTimePreciseAsFileTime() for Python time.time()?
Date User Action Args
2015-07-31 22:05:18vstinnersetrecipients: + vstinner, lemburg, tim.peters, belopolsky, pitrou, tim.golden, akira, zach.ware, steve.dower
2015-07-31 22:05:18vstinnersetmessageid: <>
2015-07-31 22:05:18vstinnerlinkissue19007 messages
2015-07-31 22:05:18vstinnercreate