Repository navigation
socket.socket.getsockname() has inconsistent UNIX/Windows behavior #45390
Description
| BPO | 1049 |
|---|---|
| Nosy | @loewis, @tpn |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = <Date 2007-08-29.16:48:05.367>
created_at = <Date 2007-08-28.23:46:32.297>
labels = ['type-bug', 'library']
title = 'socket.socket.getsockname() has inconsistent UNIX/Windows behavior'
updated_at = <Date 2008-04-10.12:40:08.754>
user = 'https://bugs.python.org/janssen'bugs.python.org fields:
activity = <Date 2008-04-10.12:40:08.754>
actor = 'trent'
assignee = 'none'
closed = True
closed_date = <Date 2007-08-29.16:48:05.367>
closer = 'loewis'
components = ['Library (Lib)']
creation = <Date 2007-08-28.23:46:32.297>
creator = 'janssen'
dependencies = []
files = []
hgrepos = []
issue_num = 1049
keywords = []
message_count = 3.0
messages = ['55390', '55425', '65280']
nosy_count = 3.0
nosy_names = ['loewis', 'janssen', 'trent']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue1049'
versions = ['Python 2.6', 'Python 3.0']
Activity
janssen commentedon Aug 28, 2007
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.
loewis commentedon Aug 29, 2007
I think it is neither possible nor "good" to produce a uniform result.
Python traditionally exposes APIs "as-is", providing the system actually
has an API with the same name. It never tries to hide differing system
behaviors in the Python wrapper; if systems vary and it is desirable to
provide a uniform API, a different API is added.
However, it is also not possible to make that uniform, as getsockname(3)
gives an unspecified result, so it is not possible for Python to
actually determine whether there was a meaningful result.
Closing as rejected.
janssen commentedon Apr 9, 2008
Here's what the OS X man page says:
The getsockname() function returns the value 0 if successful; otherwise
the value -1 is returned and the global variable errno is set to
indicate the error.