[issue9867] Interrupted system calls are not retried

[Martin v. Löwis]

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
	from -e:1

If you send SIGHUP, it will print

Hangup

So it is surely more complex than "always retry".

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue9867>
_______________________________________