消息 [241742]
Fixing the underlying connect call should also address EINTR failing with a "operation already in progress" when a connect+timeout fails due to a signal.
I can understand not addressing EINTR generically (though it is already partially addressed in 2.7's socket.py - this just completes it), but IMO, not handling it on connect & responding with a seemingly unrelated error is the wrong thing to do. |
|
| 日期 |
用户 |
动作 |
参数 |
| 2015-04-21 20:22:45 | mcjeff | 修改 | recipients:
+ mcjeff, gregory.p.smith, vstinner, benjamin.peterson, r.david.murray, koobs |
| 2015-04-21 20:22:45 | mcjeff | 修改 | messageid: <1429647765.27.0.303125640921.issue23863@psf.upfronthosting.co.za> |
| 2015-04-21 20:22:45 | mcjeff | 链接 | issue23863 messages |
| 2015-04-21 20:22:44 | mcjeff | 创建 | |
|