Closed suve closed 15 hours ago
Hi there - thanks for reporting this. I believe this is a duplicate of https://github.com/kellyjonbrazil/jc/issues/572 and will be fixed in the next release.
Edit: unless this is a new issue from 3.13 we need to address? It looks like the other issue fixed a change in 6to4 addresses but this is affecting mapped addresses. Will have to investigate.
I think this is a new issue. It affects a different test, and applying the patch from PR #573 does not help.
Looks like this is caused by:
I'm working on a fix, but have opened a cpython issue that I think might need to be addressed as well: https://github.com/python/cpython/issues/123409
https://github.com/python/cpython/issues/123409 is in process of being patched: https://github.com/python/cpython/pull/123419
It looks like the CPython issue has been addressed and will be fixed in the next 3.13 release. I have committed some changes that should fix this issue and tests when the latest Python release comes out.
https://github.com/kellyjonbrazil/jc/commit/71af0c55553e17c598c9f43b8271bfb069795af5
So, now that Python 3.13 is out - jc
v1.25.3 builds fine and all tests pass, provided one backports the following two commits: 9eb4df34b190c57d020b70153ef3faa8984c02ca and 71af0c55553e17c598c9f43b8271bfb069795af5.
As such, this issue should be fixed for everyone in the next release.
Now available in release v1.25.4
In Fedora Rawhide (the development branch / "eternal alpha" version) we've recently updated to Python 3.13.0b4 pre-release. With this new version, the following test failure can be observed:
I'm fully aware that Python 3.13.0b4 is a pre-release, which makes testing difficult, so this issue will probably have to wait until the final 3.13.0 release. You can consider this a heads-up. ;-)
For reference, the Python 3.13 "what's new" page currently lists the following changes:
Sorry for not contributing a fix, but my Python knowledge doesn't really extend past FizzBuzz level.