➜

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:01:32
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1438380093.32.0.110813200189.issue19007@psf.upfronthosting.co.za>
In-reply-to
Content 
Good news! I got a new fresh Windows 8.1 VM with Visual Studio 2015. I'm now able to work on this issue.

I wrote a patch: time_precise.patch.

Resolution computed in Python by https://hg.python.org/peps/file/tip/pep-0418/clock_resolution.py:

GetSystemTimePreciseAsFileTime(): 715 ns
GetSystemTimeAsFileTime(): 14 ms

Obviously, the resolution is better...

GetSystemTimePreciseAsFileTime() uses internally the QueryPerformanceCounter() so I chose to use QueryPerformanceFrequency() to fill time.get_clock_info('time').resolution, same code than time.get_clock_info('perf_counter').resolution
History
Date User Action Args
2015-07-31 22:01:33vstinnersetrecipients: + vstinner, lemburg, tim.peters, belopolsky, pitrou, tim.golden, akira, zach.ware, steve.dower
2015-07-31 22:01:33vstinnersetmessageid: <1438380093.32.0.110813200189.issue19007@psf.upfronthosting.co.za>
2015-07-31 22:01:33vstinnerlinkissue19007 messages
2015-07-31 22:01:33vstinnercreate