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 mcjeff
Recipients mcjeff
Date 2015-04-04.02:51:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
There are a collection of places in the socket module that do not correctly retry on EINTR.  Updated to wrap those calls in a retry loop.  However, when fixing connect calls, I noticed that when EINTR is retried on a socket with a timeout specified, the retry fails with EALREADY.. so I fixed that.

I was going to shy away from primitive calls on sockets as one expects these things when working at a lower level, however, due to the way socket timeouts were implemented, I handled it differently in internal_connect.  The create_connection calls probably ought to shield users from retry.

Python 2.7.6.
Date User Action Args
2015-04-04 02:51:25mcjeffsetrecipients: + mcjeff
2015-04-04 02:51:25mcjeffsetmessageid: <>
2015-04-04 02:51:25mcjefflinkissue23863 messages
2015-04-04 02:51:24mcjeffcreate