[New-bugs-announce] [issue1049] socket.socket.getsockname() has inconsistent UNIX/Windows behavior

[Bill Janssen]

New submission from Bill Janssen:

The behavior and return value for calling socket.socket.getsockname() on 
an unconnected unbound socket is unspecified.  On UNIX, it returns an 
address ('0.0.0.0', 0), while on Windows it raises an obscure exception 
"error: (10022, 'Invalid argument')".  This should be regularized; I'd 
suggest returning None if there is no name (address) for the socket.

----------
components: Library (Lib)
messages: 55390
nosy: janssen
priority: normal
severity: normal
status: open
title: socket.socket.getsockname() has inconsistent UNIX/Windows behavior
type: behavior
versions: Python 2.6, Python 3.0

__________________________________
Tracker <report at bugs.python.org>
<http://bugs.python.org/issue1049>
__________________________________