Message132582
> 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? |
|
Date |
User |
Action |
Args |
2011-03-30 12:25:34 | pitrou | set | recipients:
+ pitrou, kristjan.jonsson |
2011-03-30 12:25:34 | pitrou | set | messageid: <1301487934.21.0.268811861348.issue11721@psf.upfronthosting.co.za> |
2011-03-30 12:25:33 | pitrou | link | issue11721 messages |
2011-03-30 12:25:33 | pitrou | create | |
|