Message239896
| 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 |
<1427970831.87.0.198745757554.issue23618@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
test_connnect_eintr.py: 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":
https://msdn.microsoft.com/en-us/library/windows/desktop/ms741547%28v=vs.85%29.aspx
"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." |
|