[issue9867] Interrupted system calls are not retried
Martin v. Löwis
report at bugs.python.org
Thu Sep 16 14:13:10 CEST 2010
Martin v. Löwis <martin at v.loewis.de> added the comment:
Am 16.09.10 14:06, schrieb Armin Ronacher:
> Armin Ronacher<armin.ronacher at active-4.com> added the comment:
>> Hmm. So under what conditions should it continue, and under what
>> conditions should it raise an exception (when errno is EINTR)?
> EINTR indicates a temporary failure. In that case it should always retry.
But Ruby doesn't. If you send SIGINT, it will print
-e:1:in `read': Interrupt
If you send SIGHUP, it will print
So it is surely more complex than "always retry".
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list