Message 282138 - Python tracker

➜

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	<1480576883.2.0.923397246015.issue28728@psf.upfronthosting.co.za>
In-reply-to

Content
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.

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.

History
Date	User	Action	Args
2016-12-01 07:21:23	xiang.zhang	set	recipients: + xiang.zhang, vstinner, r.david.murray, SilentGhost, neologix, martin.panter
2016-12-01 07:21:23	xiang.zhang	set	messageid: <1480576883.2.0.923397246015.issue28728@psf.upfronthosting.co.za>
2016-12-01 07:21:23	xiang.zhang	link	issue28728 messages
2016-12-01 07:21:22	xiang.zhang	create