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 christian.heimes, felipecruz, giampaolo.rodola, gvanrossum, meador.inge, neologix, pitrou, rosslagerwall, sbt, vstinner
Date 2013-08-31.17:15:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377969346.57.0.887110118196.issue16853@psf.upfronthosting.co.za>
In-reply-to
Content
> Here's a patch returning [] on EINTR.

Hmm... Shouldn't it simply let the InterruptedError bubble up?
I know there's the sleep() precedent, but I find it a bit embarassing actually: the call can return early, but there's no way for the caller to know that it returned early.
History
Date User Action Args
2013-08-31 17:15:46pitrousetrecipients: + pitrou, gvanrossum, vstinner, giampaolo.rodola, christian.heimes, meador.inge, neologix, rosslagerwall, sbt, felipecruz
2013-08-31 17:15:46pitrousetmessageid: <1377969346.57.0.887110118196.issue16853@psf.upfronthosting.co.za>
2013-08-31 17:15:46pitroulinkissue16853 messages
2013-08-31 17:15:46pitroucreate