[issue12459] time.sleep(-1.0) behaviour

[STINNER Victor]

STINNER Victor <victor.stinner at haypocalc.com> 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 commit, let close this issue.

----------
resolution:  -> fixed
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12459>
_______________________________________