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 xiang.zhang
Recipients SilentGhost, martin.panter, neologix, r.david.murray, vstinner, xiang.zhang
Date 2016-12-01.07:21:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ohh, sorry.

> I was wondering if there was a separate way to detect the troublesome ISP environment.

How could you differentiate the failure between ISP environment caused and function behaved wrongly? Successfully resolve an invalid ip address doesn't mean you can successfully resolve a bogus domain.

I think this case should be rare. Maybe we can just fail the test and warn the user this failure is not 100% caused by function's misbehaviour, just like test_bad_address.
Date User Action Args
2016-12-01 07:21:23xiang.zhangsetrecipients: + xiang.zhang, vstinner, r.david.murray, SilentGhost, neologix, martin.panter
2016-12-01 07:21:23xiang.zhangsetmessageid: <>
2016-12-01 07:21:23xiang.zhanglinkissue28728 messages
2016-12-01 07:21:22xiang.zhangcreate