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 giampaolo.rodola
Recipients christian.heimes, felipecruz, giampaolo.rodola, gvanrossum, meador.inge, neologix, pitrou, rosslagerwall, sbt, vstinner
Date 2013-08-31.12:09:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I may be missing something here but isn't the whole point of EINTR to interrupt a potentially long running syscall?
Why protract function return time as a consequence?
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.
Date User Action Args
2013-08-31 12:09:35giampaolo.rodolasetrecipients: + giampaolo.rodola, gvanrossum, pitrou, vstinner, christian.heimes, meador.inge, neologix, rosslagerwall, sbt, felipecruz
2013-08-31 12:09:35giampaolo.rodolasetmessageid: <>
2013-08-31 12:09:35giampaolo.rodolalinkissue16853 messages
2013-08-31 12:09:34giampaolo.rodolacreate