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 vstinner
Recipients gvanrossum, neologix, python-dev, vstinner
Date 2014-02-11.08:14:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1392106478.18.0.294648955896.issue20505@psf.upfronthosting.co.za>
In-reply-to
Content
>> GetQueuedCompletionStatus(1 ms)->None took 0.307 ms (monotonic: 0.000 ms)
> So basically, on Windows, select(1ms) can be non-blocking?

I would not say non-blocking: it's just that select(N milliseconds) waits between N-1 and N milliseconds on Windows when HPET hardware (High Precision Event Timer) is present and enabled. Example:

GetQueuedCompletionStatus(10 ms)->None took 9.971 ms (monotonic: 0.000 ms)
History
Date User Action Args
2014-02-11 08:14:38vstinnersetrecipients: + vstinner, gvanrossum, neologix, python-dev
2014-02-11 08:14:38vstinnersetmessageid: <1392106478.18.0.294648955896.issue20505@psf.upfronthosting.co.za>
2014-02-11 08:14:38vstinnerlinkissue20505 messages
2014-02-11 08:14:37vstinnercreate