➜

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 benjamin.peterson, gregory.p.smith, koobs, mcjeff, r.david.murray, vstinner
Date 2015-04-21.20:22:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1429647765.27.0.303125640921.issue23863@psf.upfronthosting.co.za>
In-reply-to
Content 
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.
History
Date User Action Args
2015-04-21 20:22:45mcjeffsetrecipients: + mcjeff, gregory.p.smith, vstinner, benjamin.peterson, r.david.murray, koobs
2015-04-21 20:22:45mcjeffsetmessageid: <1429647765.27.0.303125640921.issue23863@psf.upfronthosting.co.za>
2015-04-21 20:22:45mcjefflinkissue23863 messages
2015-04-21 20:22:44mcjeffcreate