PEP 585: clarify removal as "no sooner than" #2778
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
See https://discuss.python.org/t/concern-about-pep-585-removals I mentioned the date explicitly so people not familiar with Python release schedule have less arithmetic to do. I also change the phrasing of the date to Python 3.9's EOL. The date remains the same. This is important because it clarifies that you don't have to write bridging code. This should also be in line with ambv's (original author) intentions; see bolded part of his message at https://discuss.python.org/t/concern-about-pep-585-removals/15901/14
hugovk
reviewed
Aug 30, 2022
Co-authored-by: Hugo van Kemenade <[email protected]>
AA-Turner
approved these changes
Aug 30, 2022
srittau
approved these changes
Aug 30, 2022
gvanrossum
approved these changes
Aug 30, 2022
|
@JelleZijlstra How's it sound now, good to merge?
|
AlexWaygood
approved these changes
Sep 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See https://discuss.python.org/t/concern-about-pep-585-removals
I mentioned the date explicitly so people not familiar with Python
release schedule have less arithmetic to do.
I also change the phrasing of the date to Python 3.9's EOL. The date
remains the same. Again, this is to help ease fear of writing 3.8 bridging
code for people who don't know Python version lifespan.
This should also be in line with ambv's (original author) intentions;
see bolded part of his message at
https://discuss.python.org/t/concern-about-pep-585-removals/15901/14