This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pyptr2
Recipients gvanrossum, pyptr2, vstinner, yselivanov
Date 2016-05-27.11:02:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464346938.98.0.196127839357.issue27136@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-05-27 11:02:19pyptr2setrecipients: + pyptr2, gvanrossum, vstinner, yselivanov
2016-05-27 11:02:18pyptr2setmessageid: <1464346938.98.0.196127839357.issue27136@psf.upfronthosting.co.za>
2016-05-27 11:02:18pyptr2linkissue27136 messages
2016-05-27 11:02:18pyptr2create