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 pitrou
Recipients kristjan.jonsson, pitrou
Date 2011-03-30.12:25:33
SpamBayes Score 0.0050449665
Marked as misclassified No
Message-id <1301487934.21.0.268811861348.issue11721@psf.upfronthosting.co.za>
In-reply-to
Content
> 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?
History
Date User Action Args
2011-03-30 12:25:34pitrousetrecipients: + pitrou, kristjan.jonsson
2011-03-30 12:25:34pitrousetmessageid: <1301487934.21.0.268811861348.issue11721@psf.upfronthosting.co.za>
2011-03-30 12:25:33pitroulinkissue11721 messages
2011-03-30 12:25:33pitroucreate