Using time.sleep() in 2 threads causes lockup when hyper-threading is enabled

Marc 'BlackJack' Rintsch bj_666 at
Fri May 5 23:20:43 CEST 2006

In <1146798159.209695.4190 at>, OlafMeding

>> 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.

The "jump" of the system clock might confuse the systems `sleep`

	Marc 'BlackJack' Rintsch

More information about the Python-list mailing list