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 pitrou
Recipients arigo, giampaolo.rodola, gregory.p.smith, gvanrossum, koobs, larry, neologix, pitrou, sbt, vstinner
Date 2013-12-01.20:03:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1385928178.2297.23.camel@fsol>
In-reply-to <>
> I do not consider this a feature; that EINTR is exposed as an
> exception from the API is a bug.

select() currently works as specified; you are proposing a
compatibility-breaking change to the API, not a bugfix.

We're left with the fact that the API is inconvenient: but we now have
the selectors module and can advocate that instead of breaking existing
code during a feature freeze period.

(or we can retry on EINTR, which has the benefit of not creating new
situations to deal with in existing code)

> The user now only has one thing to deal with instead of two: an empty
> list being returned; something they should already have been dealing
> with.

Returning an empty list when no timeout has been passed has never been a
feature of select(), which is why users are not expected to be dealing
with it.
Date User Action Args
2013-12-01 20:03:01pitrousetrecipients: + pitrou, gvanrossum, arigo, gregory.p.smith, vstinner, larry, giampaolo.rodola, neologix, sbt, koobs
2013-12-01 20:03:01pitroulinkissue18885 messages
2013-12-01 20:03:01pitroucreate