Repository navigation
gh-105578: Raise DeprecationWarning on typing.AnyStr usage - #150190
Conversation
Documentation build overview
463 files changed ·
|
AlexWaygood
left a comment
There was a problem hiding this comment.
Thanks! Wow, that came around quickly.
I had to think this through again, but I think this is correct: this is a deprecation for Python 3.16, which will become stable in autumn 2027, around the same time that Python 3.11 goes end-of-life. That means that the deprecation warnings will start to be emitted at basically the same time that the lowest non-EOL Python version is Python 3.12 -- and Python 3.12 is the first version in which users can use PEP-695 syntax
|
the test failures from the deprecation warnings in setuptools in https://github.com/python/cpython/actions/runs/26230364757/job/77188896358?pr=150190 do seem a bit concerning. Do we need to update setuptools before landing this? |
|
This PR is stale because it has been open for 90 days with no activity. |
|
Setuptools is updated, new version is released. I've fixed all merge conflicts. |
|
We can address the
I think that both have their downsides, but I would probably go with |
Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
|
I created #160824 to discuss the |
|
I fixed Please, take another look :) |
|
Thanks a lot, everyone! 🎉 |
|
Looks like this has caused buildbot refleak failures: https://buildbot.python.org/release-status For example:
The other test that does cpython/Lib/test/test_typing.py Lines 6570 to 6585 in 3feccd1 Do we need similar in |
|
Oups, sorry for that! Fixing :) |
typing.AnyStr#105578