is there better 32 clock() timing?

Michael Hoffman at mh391.invalid
Sun Jan 23 09:57:42 EST 2005

Ray Schumacher wrote:
> I have a need for a time.clock() with >0.000016 second (16us) accuracy.
> The sleep() (on Python 2.3, Win32, at least) has a .001s limit.
> Are they lower/better on other's platforms? 

The meaning of time.clock() is entirely different on other platforms. 
See the documentation. You could probably get a slight speedup by using 
"from time import clock" and then just clock().
Michael Hoffman

More information about the Python-list mailing list