In <[EMAIL PROTECTED]>, OlafMeding wrote: >> 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`
implementation.
Ciao,
Marc 'BlackJack' Rintsch
--
http://mail.python.org/mailman/listinfo/python-list
