[issue27822] Fail to create _SelectorTransport with unbound socket

STINNER Victor added the comment: > In writing a simple UDP client using asyncio, I tripped over a call to > getsockname() in the _SelectorTransport class in asyncio/selector_events.py. > (...) This bug has been fixed recently by: commit 63deaa5b70108ef441c57728322da6b4321db4fc Author:

[issue27822] Fail to create _SelectorTransport with unbound socket

Paul McGuire added the comment: Patch file attached. -- keywords: +patch Added file: http://bugs.python.org/file44182/ptm_27822.patch ___ Python tracker

[issue27822] Fail to create _SelectorTransport with unbound socket

Guido van Rossum added the comment: Can you supply a patch yourself? --Guido (mobile) -- ___ Python tracker ___

[issue27822] Fail to create _SelectorTransport with unbound socket

Paul McGuire added the comment: (issue applies to both 3.5.2 and 3.6) -- versions: +Python 3.5 ___ Python tracker ___

[issue27822] Fail to create _SelectorTransport with unbound socket

Paul McGuire added the comment: To clarify how I'm using a socket without a bound address, I am specifying the destination address in the call to transport.sendto(), so there is no address on the socket itself, hence getsockname() fails. -- ___

[issue27822] Fail to create _SelectorTransport with unbound socket

New submission from Paul McGuire: In writing a simple UDP client using asyncio, I tripped over a call to getsockname() in the _SelectorTransport class in asyncio/selector_events.py. def __init__(self, loop, sock, protocol, extra=None, server=None): super().__init__(extra, loop)