Message204912
| Author |
neologix |
| Recipients |
arigo, giampaolo.rodola, gregory.p.smith, gvanrossum, koobs, neologix, pitrou, sbt, vstinner |
| Date |
2013年12月01日.11:33:45 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAH_1eM1xc6G2sR-MNbNJ1BF6cPSKHiE8pTD1-dvjemO6dZnuMw@mail.gmail.com> |
| In-reply-to |
<1385894817.2297.8.camel@fsol> |
| Content |
> Well this is wishing thinking, since by returning an empty list you
> force the user to handle EINTR - just in a different way.
I know that returning an empty list changes the semantics: I just
think that's better - or not as bad - than the current possibility of
having any single piece of code possibly die upon EINTR.
If you want to implement retry with timeout re-computation, I'm not
the one to who must be convinced :-)
(BTW, if we go this way, then time.sleep() should probably also be
fixed to retry upon EINTR). |
|