Eryk Sun added the comment:
> What are the expected benefits from changing? Just a higher
> resolution? I'm not sure that's worth anything if it's inaccurate.
GetSystemTimePreciseAsFileTime() returns an accurate timestamp, which is the
current system time plus the difference between the
Steve Dower added the comment:
What are the expected benefits from changing? Just a higher resolution? I'm not
sure that's worth anything if it's inaccurate.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19007
STINNER Victor added the comment:
Note: GetSystemTimePreciseAsFileTime() is restricted to desktop applications.
The windowstimestamp.com has a warning on this function:
http://www.windowstimestamp.com/description
2.1.4.2. Desktop Applications: GetSystemTimePreciseAsFileTime()
(...)
The
STINNER Victor added the comment:
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:
STINNER Victor added the comment:
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
Changes by Akira Li 4kir4...@gmail.com:
--
nosy: +akira
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19007
___
___
Python-bugs-list mailing list
Changes by STINNER Victor victor.stin...@gmail.com:
--
title: precise time.time() under Windows 8 - precise time.time() under Windows
8: use GetSystemTimePreciseAsFileTime
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19007
