gh-93626: Set the release for __future__.annotations to 3.12
#93628
+5
∄1�71
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
|
The following commit authors need to sign the Contributor License Agreement: Click the button to sign: |
|
I think your CLA facility is busted, when I sign it, it just says:
|
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.
Hi everyone, I noticed that😳 😳 😳 😳 😳 😳 .
__future__.annotationswas turned on in the 3.11 betasThis is highly sus as it should be turned off till further notice (3.12
).
This is my first cpython contrib, I tried to follow the contributing process, but maybe I missed something, sorry!
This PR also needs to be backported to the 3.11 branch
resolves: #93626