[issue17683] socket.getsockname() inconsistent return type with AF_UNIX
Charles-François Natali
report at bugs.python.org
Tue May 21 10:37:40 CEST 2013
Charles-François Natali added the comment:
Hum, IIUC, basically what happens is that the user could - and still
can - pass arbitrary bytes as address (which is legtit), but depending
on the encoding, getsockaddr() and friends might blow up when decoding
it.
If that's correct, that's bad, and that would be a good reason to keep bytes.
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue17683>
_______________________________________
More information about the Python-bugs-list
mailing list