Re: time.clock() problem under linux (precision=0.01s)

2005-08-19 Thread Adriaan Renting
One of the limits of at least IBM compatible PC's is that in general they are not more accurate as about 1/64 th of a second if I recall correctly. I think this is the default tick size of the BIOS clock. Next to that the BIOS clock itself doesn't need to be very accurate, I can easily drift lik

Re: time.clock() problem under linux (precision=0.01s)

2005-08-18 Thread ncf
Woa, if you don't mind my asking, why do you do a time-cache on your messages? -- http://mail.python.org/mailman/listinfo/python-list

Re: time.clock() problem under linux (precision=0.01s)

2005-08-18 Thread Mike Meyer
"Szabolcs Nagy" <[EMAIL PROTECTED]> writes: > time.time seems much better solution, but python manual sais: "not all > systems provide time with a better precision than 1 second" > > Should i use time.clock or time.time to be more crossplatform? > Is time.time ok for windows? (time()-time() != 0.0