➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients gvanrossum, neologix, vstinner
Date 2014-02-06.20:06:25
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJK2QUKZdXvBFK4rkEd-rDJd4PZa73TUQ35YCymeqR=Spg@mail.gmail.com>
In-reply-to <CAH_1eM1ErWvdLyu30jCwUc0xWZ73sUM54FFs=MHsLEbqXv6n6g@mail.gmail.com>
Content 
>
> Let me state this last point once again: no busy loop can occur now that
> timeouts are rounded up.
>

How sure are you? Suppose I use poll() with a 0.5 msec timeout. This
presumably gets rounded up to 1 msec. But if the system clock has e.g. a 10
msec resolution, won't this still wait 0 msec? Or will it wait until the
next "tick" occurs, which could be anywhere between 0 and 10 msec in the
future? But if so, why wouldn't a poll() with a 0 msec timeout also wait
between 0 and 10 msec?
History
Date User Action Args
2014-02-06 20:06:25gvanrossumsetrecipients: + gvanrossum, vstinner, neologix
2014-02-06 20:06:25gvanrossumlinkissue20505 messages
2014-02-06 20:06:25gvanrossumcreate