-
Notifications
You must be signed in to change notification settings - Fork 206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python 3.12 test regression: tests.test_ip_address.MyTests.test_ip_address_ipv6_6to4
#572
Comments
Hi, thanks for reporting this! I'm seeing tests passing for Python 3.12 in Github Actions. Maybe it's a difference in underlying hardware? |
I've been able to reproduce it both in Gentoo packaging process that uses an isolated network namespace with just the loopback interface, and on my regular system. The ifconfig from the test setup is:
|
I've got another data point: the test passes with Python 3.12.3 but fails with 3.12.4. FWICS GitHub Actions are stuck on .3 for some reason. The log for 3.12.4 says:
|
Thanks! I'll have to figure out how to update the tests for this. |
This seems to be cause by python/cpython@f86b17a, particularly: + # IANA says N/A, let's consider it not globally reachable to be safe
+ IPv6Network('2002::/16'), Perhaps the simplest solution would be to avoid this particular range, since it's "undefined" by IANA. |
Good call! Thanks for the research. |
Hmmm... after looking at this I'm not sure if I can use another range because this test is specifically testing 6to4 addressing which is in this network space. I may just need to do a python version check and allow either value depending on the version. |
Ah, right then. According to the documentation, the results changed in 3.12.4 and 3.13.0, so I guess you can just check for |
@kellyjonbrazil I am also seeing this test failure in Debian. |
I'm going to try making a pull request. |
Adjust the expected output in `test_ip_address_ipv6_6to4` to account for `is_global`/`is_private` changes for 6to4 addresses in Python 3.12.4 and Python 3.13.0. Fixes kellyjonbrazil#572
Thanks for the PR - I'll get that in the next release. |
) Adjust the expected output in `test_ip_address_ipv6_6to4` to account for `is_global`/`is_private` changes for 6to4 addresses in Python 3.12.4 and Python 3.13.0. Fixes #572 Co-authored-by: Kelly Brazil <kellyjonbrazil@gmail.com>
When running the test suite under Python 3.12.4, the following test fails:
It seems to pass with 3.11 and older.
Note I had to add
maxDiff = None
to get a diff there.The text was updated successfully, but these errors were encountered: