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 virtual machine inside same host - with Centos 6.3: getaddrinfo returns -2 (invalid host address). This seems to be the behaviour expected by Python. * VM with Ubuntu 13.04 (vanilla live CD) - again 110 (Connection timed out). Since vanilla live CD is affected: I suppose it's not supposed to be something specific to my OS config. ---------- nosy: +javornikolov _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue17759> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com