➜

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-21.10:50:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1437475856.88.0.682110111748.issue19007@psf.upfronthosting.co.za>
In-reply-to
Content 
Python 3.5 has a new C function _PyTime_GetSystemClock() which uses the new _PyTime_t type. It now has a resolution of 1 nanosecond.

Sorry, I don't have Windows 8 at home, so I cannot work on this issue.

I guess that we should check at runtime if GetSystemTimePreciseAsFileTime() is available, as we did for GetTickCount64() in the past:

hKernel32 = GetModuleHandleW(L"KERNEL32");
*(FARPROC*)&Py_GetTickCount64 = GetProcAddress(hKernel32,
                                               "GetTickCount64");

Is there any Windows developer interested to write a short patch to implement it?
History
Date User Action Args
2015-07-21 10:50:56vstinnersetrecipients: + vstinner, lemburg, tim.peters, belopolsky, pitrou, tim.golden, akira, zach.ware, steve.dower
2015-07-21 10:50:56vstinnersetmessageid: <1437475856.88.0.682110111748.issue19007@psf.upfronthosting.co.za>
2015-07-21 10:50:56vstinnerlinkissue19007 messages
2015-07-21 10:50:56vstinnercreate