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 gregory.p.smith
Recipients gregory.p.smith, neologix, pitrou, sbt, vstinner
Date 2013-08-31.16:44:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
FYI - use the changes made in as a guide for how to deal with EINTR properly at the C level.  See the _PyIO_trap_eintr() function for example.

See also _eintr_retry_call() in Lib/

FWIW, there are times when we *want* the interrupted system call to return control to Python rather than retrying the call.  If someone is making a Python equivalent of the low level system call such as select() or poll(), the EINTR should be exposed for Python code to handle.

Things like time.sleep() are documented as sleeping for less time when a signal has arrived even though an exception may not be raised. People have written code which depends on this behavior so adding an EINTR retry for the remaining sleep time would break some programs.

Getting an EINTR errno does *not* mean you can simply retry the system calls with the exact same arguments.  ie: If you did that with the select() call within time.sleep it'd be trivial to make the process sleep forever by sending it signals with a frequency less than the sleep time.
Date User Action Args
2013-08-31 16:44:13gregory.p.smithsetrecipients: + gregory.p.smith, pitrou, vstinner, neologix, sbt
2013-08-31 16:44:13gregory.p.smithsetmessageid: <>
2013-08-31 16:44:13gregory.p.smithlinkissue18885 messages
2013-08-31 16:44:13gregory.p.smithcreate