Marc > IIRC it was something like an NTP daemon that caused the clock to "jump" a > little and (Window's) sleep was confused.
The problem is not a "jump" but a permanet lockup of the sleep statement. To all others, is there nobody out there that could run the test code at the beginning of this post on a hyper-threading CPU? Olaf -- http://mail.python.org/mailman/listinfo/python-list
