New submission from Barry A. Warsaw <[email protected]>:
This is very likely caused by something janky my ISP (AT&T) is doing with IPv6,
but the above named test fails for me because IPv6 addresses like `::1q` do not
fail to resolve as the test expects.
I'm not sure what can or should be done about it, but as this is an annoying
local failure, and I couldn't find another mention of it by searching bpo, I
wanted to at least get it on record.
The test function's comment says:
"
# These are all malformed IP addresses and expected not to resolve to
# any result. But some ISPs, e.g. AWS, may successfully resolve these
# IPs.
"
So apparently, put AT&T in that bucket of ISPs that resolve those IPv6
addresses.
----------
messages: 379020
nosy: barry
priority: normal
severity: normal
status: open
title: test_host_resolution_bad_address does not always fail as expected
versions: Python 3.10, Python 3.7, Python 3.8, Python 3.9
_______________________________________
Python tracker <[email protected]>
<https://bugs.python.org/issue42092>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
