[Python-Dev] time.sleep(-1) behaviour (original) (raw)
Tim Lesher tlesher at gmail.com
Fri Jul 1 15:23:17 CEST 2011
- Previous message: [Python-Dev] time.sleep(-1) behaviour
- Next message: [Python-Dev] time.sleep(-1) behaviour
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jul 1, 2011 at 08:46, Nick Coghlan <ncoghlan at gmail.com> wrote:
For Sleep, yes, but the time.sleep() docs [1] are completely silent on the behaviour of negative sleep values at the Python level. Question 3 isn't "Is there something wrong with Sleep()?", it is "Is there something wrong with the way time.sleep() uses Sleep()?"
That makes sense. Better to be consistent within the time API--I know the different semantics of time.clock() have confused people around here.
-- Tim Lesher <tlesher at gmail.com>
- Previous message: [Python-Dev] time.sleep(-1) behaviour
- Next message: [Python-Dev] time.sleep(-1) behaviour
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]