gh-82786: Set the release for __future__.annotations to 3.12 - #94501
Closed
asottile wants to merge 1 commit into
Closed
gh-82786: Set the release for __future__.annotations to 3.12#94501asottile wants to merge 1 commit into
__future__.annotations to 3.12#94501asottile wants to merge 1 commit into
Conversation
asottile
force-pushed
the
future-annotations-not-in-3-11
branch
from
July 1, 2022 18:44
d02a78c to
ef79d83
Compare
__future__.anntations to 3.12__future__.annotations to 3.12
Member
|
There is another PR dealing with this if I am not mistaken |
Member
|
#93626 if I am not mistaken |
Contributor
Author
|
fine with me! just as long as it's a release blocker 🎉 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
same as #25596
just kicking the can down the road once again -- this should also land in 3.11 before that releases CC @pablogsal