GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — gh-105578: Raise `DeprecationWarning` on `typing.AnyStr` usage by sobolevn · Pull Request #150190 · python/cpython Conversation
|
Documentation build overview
463 files changed ·
|
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
The reason will be displayed to describe this comment to others. Learn more.
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.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
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.
There was an error while loading. Please reload this page.
|
This PR is stale because it has been open for 90 days with no activity. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Setuptools is updated, new version is released. I've fixed all merge conflicts. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
We can address the
I think that both have their downsides, but I would probably go with |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Co-authored-by: Hugo van Kemenade <[email protected]>
|
I created #160824 to discuss the |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
I fixed Please, take another look :) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
Thanks a lot, everyone! 🎉 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
|
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 |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
|
Oups, sorry for that! Fixing :) |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.