bpo-40360: [doc] Rephrase deprecation note about lib2to3 #28122
Merged
Conversation
This file contains hidden or 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
vstinner approved these changes Sep 2, 2021
Member
vstinner left a comment
vstinner left a comment There was a problem hiding this comment.
LGTM, thanks.
I didn't touch the doc, since I didn't know if we still could deprecate in 3.10, or if 3.11 was a more reasonable option (it is).
Contributor
| Thanks @ambv for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10. |
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Sep 2, 2021
) (cherry picked from commit f0b63d5) Co-authored-by: Łukasz Langa <lukasz@langa.pl>
| GH-28127 is a backport of this pull request to the 3.10 branch. |
miss-islington added a commit that referenced this pull request Sep 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants
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.
The previous wording was written in a future tense and incorrectly assumed we would fully deprecate lib2to3 in Python 3.10 but we missed the boat for that.
https://bugs.python.org/issue40360