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 gregory.p.smith
Recipients gregory.p.smith, mcjeff, vstinner
Date 2015-04-07.22:48:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I like the socketmodule.c part of socket_eintr.1.patch, but it appears to still have the issue haypo describes in where connect() cannot be called more than once.  The kernel carries on with the connect without our process waiting for it, we have to monitor it to know when it has succeeded or failed.

See and issue23618 from Python 3.5.

[code review done at 35,000ft, thanks chromebook gogo free wifi pass!]
Date User Action Args
2015-04-07 22:48:17gregory.p.smithsetrecipients: + gregory.p.smith, vstinner, mcjeff
2015-04-07 22:48:17gregory.p.smithsetmessageid: <>
2015-04-07 22:48:17gregory.p.smithlinkissue23863 messages
2015-04-07 22:48:17gregory.p.smithcreate