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 <>
> 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:

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:
(I wrote it and I didn't test my change, I didn't know how to test it.)
Tulip issue:
Date User Action Args
2015-03-09 09:20:02vstinnersetrecipients: + vstinner, neologix, serhiy.storchaka
2015-03-09 09:20:02vstinnersetmessageid: <>
2015-03-09 09:20:02vstinnerlinkissue23618 messages
2015-03-09 09:20:01vstinnercreate