Yavor added the comment:
I have the same problem. Reproduced via custom app and what's failing is:
getaddrinfo("some.invalid.address.here", NULL, &hints, &result);
And it's failing quickly. But the returned error is system error 110
(Connection timed out).
* A
Yavor added the comment:
* Up-to-date Arch Linux: -2 - Name or service not known
* Fedora Live CD: -2 - Name or service not known
These are in general with more recent libraries/packages than Ubuntu 13.04. All
evidences suggest that there is something abnormal with this Ubuntu release
Yavor added the comment:
Reported the issue to Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1198744
--
___
Python tracker
<http://bugs.python.org/issue17
Yavor added the comment:
Within this note https://sourceware.org/glibc/wiki/NameResolver about
getaddrinfo():
"In case there was a *negative* answer it's unclear what should be returned."
--
___
Python tracker
<http://bugs.pyt
New submission from Yavor Atov :
>From
>https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.sock_connect
> :
Changed in version 3.5.2: address no longer needs to be resolved. sock_connect
will try to check if the address is already resolved by calling
socket.
