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, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2014-01-23.23:25:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <1390518490.2293.32.camel@fsol>
Le 24 janv. 2014 00:08, "Antoine Pitrou" <> a écrit :
> > For example, it may call again epoll_wait() if it took less than timeout
> > seconds and returned no event, *and* the ready list is empty.
> Easy solution: add 1 ms. to the timeout before calling epoll_wait().
> Perhaps we need the same kind of thing for select() and poll() too.

It doesn't fix the case when got an InterruptedError.

Adding 1 ms works around the (now fixed) timeout rounding issue but I
prefered to round differently to not sleep longer than requested (try to
respect deadline).

About the "system clock", it's possibke than Linux uses a different clock
for epoll_wait() than CLOCK_MONOTONIC, and than clocks have a different

I didn't test the rounding issue on Windows where time.monotonic() has a
resolution between... 1 and 16 ms!
Date User Action Args
2014-01-23 23:25:57vstinnersetrecipients: + vstinner, gvanrossum, pitrou, neologix, python-dev, serhiy.storchaka
2014-01-23 23:25:57vstinnerlinkissue20311 messages
2014-01-23 23:25:56vstinnercreate