This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jtate
Date 2007-03-28.15:07:43
SpamBayes Score
Marked as misclassified
On Linux time.clock() is CPU time.  And has no bearing at all on real time.  On windows time.clock() is real time since CPU time is not available from the operating system.

What if instead of replacing time.time() with time.clock(), the Queue and Event wait loops just kicked out if "remaining time" was larger than the initial wait time?  Let the outer loop continue, and the next time wait is called, the "remaining time" will be calculated correctly.

Otherwise, we could compare "remaining time" between one loop iteration and the subsequent and then *approximate* how much the time has changed to adjust the "end time" appropriately.
Date User Action Args
2007-08-23 14:40:42adminlinkissue1508864 messages
2007-08-23 14:40:42admincreate