Ned Deily added the comment:
As I commented over on Issue7322, I think any such test would be not perfect
since I believe the blocking status of the socket could be changed at any time,
at least on Unix-y systems. So I'm +0 on whether adding a test in makefile()
is worth it, presuming it can
Roy Smith added the comment:
Thank you for the detailed analysis. That certainly explains what I observed.
Would it make sense for socket.makefile() to check to see if the socket is in
blocking mode (assuming there is some reliable/portable way to perform this
check), and raise some exceptio
Ned Deily added the comment:
There is a difference in behavior in the accept() socket call between Linux and
BSD systems (including OS X). As documented in the Debian Linux man page for
accept(2): "On Linux, the new socket returned by accept() does not inherit
file status flags such as O_NON
New submission from Roy Smith :
While investigating issue7322, I wrote a test case to demonstrate the issue. I
made a mistake and called settimeout() on the wrong socket, but the result
appears to demonstrate a different bug. When I run the attached
test-issue7322.py on my OSX-10.6.5 machine
