[issue28447] socket.getpeername() failure on broken TCP/IP connection

R. David Murray report at bugs.python.org
Thu Oct 20 10:57:01 EDT 2016


R. David Murray added the comment:

Unless I'm missing something, this indicates that the problem is that once the far end closes, Windows will no longer return the peer name.  

And, unless I'm misreading, the behavior will be the same on Unix.  The man page for getpeername says that ENOTCONN is returned if the socket is not connected.

This isn't a bug in Python.  Or Windows, though the error message is a bit counter-intuitive to a unix programmer.

----------
nosy: +r.david.murray
resolution: wont fix -> not a bug
stage: test needed -> resolved
status: open -> closed

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue28447>
_______________________________________


More information about the Python-bugs-list mailing list