RetroSearch Browse

Wed Oct 21 22:51:03 CEST 2009 · http://mail.python.org/pipermail/python-dev/2009-October/093141.html

Kristján Valur Jónsson <kristjan <at> ccpgames.com> writes:
> 
> You are right, on windows time.clock() is based relative to its first call in
the process.  There is no such
> promise made on unix.
> QueryPerformanceCounter() (what time.clock uses()) is a robust high resolution
timer that is
> processor/core independent.  It should be possible to use it across different
processes too, if this
> annoying rebasing wasn't there.

Well, could we simply have a high-resolution time.time()?
Or is Windows just too limited to provide this?

Regards

Antoine.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2009-October/093141.html below:

[Python-Dev] time.clock() on windows