[Python-Dev] Rename time.steady(strict=True) to time.monotonic()? (original) (raw)
Victor Stinner victor.stinner at gmail.com
Sat Mar 24 01:45:37 CET 2012
- Previous message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Next message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- time.clock(): monotonic clock on Windows, CPU time on UNIX
Actually, I think that is not correct. Or at least was not correct in 2006. http://bytes.com/topic/python/answers/527849-time-clock-going-backwards
Oh, I was not aware of this issue. Do you suggest to not use QueryPerformanceCounter() on Windows to implement a monotonic clock?
The python-monotonic-time project uses GetTickCount64(), or GetTickCount(), on Windows. GetTickCount64() was added to Windows Seven / Server 2008. GetTickCount() overflows after 49 days. QueryPerformanceCounter() has a better resolution than GetTickCount64.
Victor
- Previous message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Next message: [Python-Dev] Rename time.steady(strict=True) to time.monotonic()?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]