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 neologix, pitrou, python-dev, serhiy.storchaka, vstinner
Date 2015-04-02.10:33:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Content program to interrupt socket.connect() with signals. It looks like socket.connect() cannot be interrupted by signals: connect() only fails with WSAEINTR when WSACancelBlockingCall() is called, but WSACancelBlockingCall() "has been removed in compliance with the Windows Sockets 2 specification, revision 2.2.0":

"Blocking hooks are generally used to keep a single-threaded GUI application responsive during calls to blocking functions. Instead of using blocking hooks, an applications should use a separate thread (separate from the main GUI thread) for network activity."
Date User Action Args
2015-04-02 10:33:51vstinnersetrecipients: + vstinner, pitrou, neologix, python-dev, serhiy.storchaka
2015-04-02 10:33:51vstinnersetmessageid: <>
2015-04-02 10:33:51vstinnerlinkissue23618 messages
2015-04-02 10:33:51vstinnercreate