➜

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 vstinner
Recipients gvanrossum, vstinner, yselivanov
Date 2015-04-07.08:23:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1428394989.42.0.151918238179.issue23879@psf.upfronthosting.co.za>
In-reply-to
Content 
According to the issue #23618, when connect() fails with EINTR, retrying connect() may only work on some platforms. To have a reliable behaviour on all platforms, we should wait until the socket becomes writable because the connection runs asynchronously in background. When the socket becomes writable, we have to gets its error code (getsockopt(SO_ERROR)) to check if the connection succeeded or failed.

Attached patch fixes SelectorEventLoop.sock_connect().
History
Date User Action Args
2015-04-07 08:23:09vstinnersetrecipients: + vstinner, gvanrossum, yselivanov
2015-04-07 08:23:09vstinnersetmessageid: <1428394989.42.0.151918238179.issue23879@psf.upfronthosting.co.za>
2015-04-07 08:23:08vstinnerlinkissue23879 messages
2015-04-07 08:23:08vstinnercreate