[issue12459] time.sleep(-1.0) behaviour

2011-07-05 Thread STINNER Victor
STINNER Victor added the comment: Tim Lesher agreed to raise an exception ("That makes sense. Better to be consistent within the time API--I know the different semantics of time.clock() have confused people around here."), so I think that everybody agreed to raise an exception. I commited my

[issue12459] time.sleep(-1.0) behaviour

2011-07-05 Thread Roundup Robot
Roundup Robot added the comment: New changeset 0e5485634817 by Victor Stinner in branch 'default': Issue #12459: time.sleep() now raises a ValueError if the sleep length is http://hg.python.org/cpython/rev/0e5485634817 -- nosy: +python-dev ___ Python

[issue12459] time.sleep(-1.0) behaviour

2011-07-02 Thread Jesús Cea Avión
Changes by Jesús Cea Avión : -- nosy: +jcea ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread Santoso Wijaya
Changes by Santoso Wijaya : -- nosy: +santa4nt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread Daniel Urban
Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread STINNER Victor
STINNER Victor added the comment: Tim Lesher on python-dev: "On the Windows side, Sleep(-1) as "infinite" is correct and documented: http://msdn.microsoft.com/en-us/library/ms686298(v=vs.85).aspx" Wine defines INFINITE using "#define INFINITE 0x": http://source.winehq.org/source/includ

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread STINNER Victor
STINNER Victor added the comment: See also #12462, I found something weird in the signal handling of floatsleep(). -- ___ Python tracker ___

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread STINNER Victor
STINNER Victor added the comment: > According to Google Code Search, deliberate uses of sleep(-1) > are almost non-existent: The search gives two results, in pycaf and a plone installer (in "compilezpy.py"). I don't know what is the expected behaviour: "infinite" sleep? wait for a SIGINT sign

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread Antoine Pitrou
Antoine Pitrou added the comment: I agree with the ValueError suggestion. Since it would slightly change existing behaviour, it can only be done in a feature release (3.3). According to Google Code Search, deliberate uses of sleep(-1) are almost non-existent: http://www.google.com/codesearch#

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread STINNER Victor
STINNER Victor added the comment: I think that time.sleep() should behave as select.select() (issue #11757, commit 3982be773b54) and signal.sigtimedwait(): raise a ValueError if the timeout is negative. A good reason to always raise an error is that floatsleep() has different implementations.

[issue12459] time.sleep(-1.0) behaviour

2011-07-01 Thread Raymond Hettinger
Changes by Raymond Hettinger : -- assignee: -> rhettinger nosy: +rhettinger priority: normal -> low ___ Python tracker ___ ___ Python

[issue12459] time.sleep(-1.0) behaviour

2011-06-30 Thread Ulrich Eckhardt
New submission from Ulrich Eckhardt : For reference, see the thread on the users' mailinglist/newsgroup from 2011-06-29 "how to call a function for evry 10 seconds" and the thread on the developers' mailinglist from 2011-06-30 "time.sleep(-1) behaviour". The problem is how negative arguments t