July 1, 2011
1:23 p.m.
On Fri, Jul 1, 2011 at 08:46, Nick Coghlan <ncoghlan@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@gmail.com>