New submission from pyptr2: Base{Selector,Proactor}EventLoop each have a sock_connect() method, both of which unconditionally "try" to run base_events' _check_resolved_address() which is apparently meant to raise an exception when called with an unresolved IP hostname. (because on some OSes it cannot be done asynchronously? WTF?)
Anyhow, the current implementation prevents ANY address family other than IP (and UNIX, which is special cased) to raise the exception, no matter if it's resolved or not. So please, call _ipaddr_info() for IP only. ---------- components: asyncio files: check_resolved.patch keywords: patch messages: 266486 nosy: gvanrossum, haypo, pyptr2, yselivanov priority: normal severity: normal status: open title: sock_connect fails for bluetooth (and probably others) type: behavior versions: Python 3.6 Added file: http://bugs.python.org/file43027/check_resolved.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27136> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com