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:23:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1377951776.2478.10.camel@fsol>
In-reply-to <>
> I may be missing something here but isn't the whole point of EINTR to
> interrupt a potentially long running syscall?

Not exactly. The point is to signal (!) that a signal was received.
The received signal is not necessarily expected.

Also, from what I understand, it is more reliable to use a wakeup fd
(using e.g. signal.set_wakeup_fd) rather than expect EINTR to be
Date User Action Args
2013-08-31 12:23:07pitrousetrecipients: + pitrou, gvanrossum, vstinner, giampaolo.rodola, christian.heimes, meador.inge, neologix, rosslagerwall, sbt, felipecruz
2013-08-31 12:23:07pitroulinkissue16853 messages
2013-08-31 12:23:07pitroucreate