Le vendredi 01 juillet 2011 à 08:17 -0400, Tim Lesher a écrit : > On Thu, Jun 30, 2011 at 15:13, Ulrich Eckhardt > <ulrich.eckha...@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
I answered on the bug tracker: http://bugs.python.org/issue12459 Victor _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
