1 Jul
2011
1 Jul
'11
12:17 p.m.
On Thu, Jun 30, 2011 at 15:13, Ulrich Eckhardt <ulrich.eckhardt@dominolaser.com> wrote:
Hi!
This is a request for clarification for the thread "how to call a function for evry 10 seconds" from the user mailinglist/newsgroup.
The gist is this: 1. On Linux/Python 2.6, time.sleep(-1.0) raises an IOError. 2. On MS Windows/Python 2.5 or 2.7 this sleeps forever. It seems that converting this to a 32-bit integer for Sleep() causes an underflow.
3. Is the behaviour under MS Windows acceptable or a bug?
On the Windows side, Sleep(-1) as "infinite" is correct and documented: http://msdn.microsoft.com/en-us/library/ms686298(v=vs.85).aspx -- Tim Lesher <tlesher@gmail.com>