Antoine Pitrou <pit...@free.fr> added the comment: > In short: If you have a socket with settimeout(1), then accept a > connection on it, the new socket will have gettimeout()==None, but its > state will still (internally) be non-blocking. The attached script > demonstrates the issue.
This should have been fixed in ed0259230611. Can you confirm? ---------- nosy: +pitrou _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue11721> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
