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.12:26:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377951952.2478.11.camel@fsol>
In-reply-to <>
> All the event loops I'm familiar with (twisted, tornado and asyncore)
> just 'return' on EINTR, supposedly because that was the best
> compromise to support syscall interruption without forcing users to
> handle EINTR themselves.

What do you mean? Tornado simply retries on EINTR:
Date User Action Args
2013-08-31 12:26:00pitrousetrecipients: + pitrou, gvanrossum, vstinner, giampaolo.rodola, christian.heimes, meador.inge, neologix, rosslagerwall, sbt, felipecruz
2013-08-31 12:26:00pitroulinkissue16853 messages
2013-08-31 12:26:00pitroucreate