gh-105578: Raise DeprecationWarning on typing.AnyStr usage#150190
gh-105578: Raise DeprecationWarning on typing.AnyStr usage#150190sobolevn wants to merge 2 commits into
DeprecationWarning on typing.AnyStr usage#150190Conversation
Documentation build overview
8 files changed ·
|
Sorry, something went wrong.
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
Sorry, something went wrong.
|
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? |
Sorry, something went wrong.
typing.AnyStr#105578