[issue8831] recv and recvfrom on UDP socket do not return/throw exception after a close()

New submission from Alessandro Roat : A thread blocked on a recv or a recvfrom method on a UDP socket (waiting for a datagram) can not be unlocked calling a .close() from a different thread. This is in contrast with the standard C++/C behavior, where a close() on a socket causes an

[issue8831] recv and recvfrom on UDP socket do not return/throw exception after a close()

Alessandro Roat added the comment: This is an example, test it with netcat (nc -u localhost ) on linux (ubuntu 9.10). Lauch it with python , a prompt will appear. Type "start" to launch the server, test the server sending UDP packets with netcat, the lenght of packet will be