Message 237616 - Python tracker

➜

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	vstinner
Recipients	neologix, serhiy.storchaka, vstinner
Date	2015-03-09.09:20:01
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1425892802.16.0.262196026845.issue23618@psf.upfronthosting.co.za>
In-reply-to

Content
> If EINTR is received during connect, the socket is unusable, > that's why i didn't implement it. Can you elaborate? socket.connect() should be modified according to the PEP 475: https://www.python.org/dev/peps/pep-0475/#modified-functions What do you mean by "unusable"? Is it possible to retry connect()? Is it safe to call getsockopt(fd, SOL_SOCKET, SO_ERROR) until it returns EISCONN? For high-level functions for socket.create_connection(), how should we handle InterruptedError? See also this change in asyncio to handle InterruptedError in asyncio: https://hg.python.org/cpython/rev/ad67f66a5f3c (I wrote it and I didn't test my change, I didn't know how to test it.) Tulip issue: https://code.google.com/p/tulip/issues/detail?id=205

> If EINTR is received during connect, the socket is unusable,
> that's why i didn't implement it.

Can you elaborate?

socket.connect() should be modified according to the PEP 475:
https://www.python.org/dev/peps/pep-0475/#modified-functions

What do you mean by "unusable"? Is it possible to retry connect()? Is it safe to call getsockopt(fd, SOL_SOCKET, SO_ERROR) until it returns EISCONN?

For high-level functions for socket.create_connection(), how should we handle InterruptedError?

See also this change in asyncio to handle InterruptedError in asyncio:
https://hg.python.org/cpython/rev/ad67f66a5f3c
(I wrote it and I didn't test my change, I didn't know how to test it.)
Tulip issue: https://code.google.com/p/tulip/issues/detail?id=205

History
Date	User	Action	Args
2015-03-09 09:20:02	vstinner	set	recipients: + vstinner, neologix, serhiy.storchaka
2015-03-09 09:20:02	vstinner	set	messageid: <1425892802.16.0.262196026845.issue23618@psf.upfronthosting.co.za>
2015-03-09 09:20:02	vstinner	link	issue23618 messages
2015-03-09 09:20:01	vstinner	create