Message240044
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:25 | mcjeff | set | recipients:
+ mcjeff |
2015-04-04 02:51:25 | mcjeff | set | messageid: <1428115885.34.0.897753768137.issue23863@psf.upfronthosting.co.za> |
2015-04-04 02:51:25 | mcjeff | link | issue23863 messages |
2015-04-04 02:51:24 | mcjeff | create | |
|