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 javornikolov
Recipients barry, doko, javornikolov, r.david.murray
Date 2013-07-07.20:03:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373227418.83.0.201253506105.issue17759@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2013-07-07 20:03:38javornikolovsetrecipients: + javornikolov, barry, doko, r.david.murray
2013-07-07 20:03:38javornikolovsetmessageid: <1373227418.83.0.201253506105.issue17759@psf.upfronthosting.co.za>
2013-07-07 20:03:38javornikolovlinkissue17759 messages
2013-07-07 20:03:38javornikolovcreate