[3.8] bpo-41314: fixed annotations __future__ version (GH-21616) #21621
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
PEP 563 was updated to change the release where `from __future__ import annotations` becomes the default (and only) behavior from 4.0 to 3.10. Update `__future__.py` and its docs to reflect this. (cherry picked from commit 0028c14) Co-authored-by: YoSTEALTH <[email protected]>
gvanrossum
approved these changes
Jul 25, 2020
|
@YoSTEALTH: Status check is done, and it's a success ✅ . |
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.
PEP 563 was updated to change the release where
from __future__ import annotationsbecomes the default (and only) behavior from 4.0 to 3.10. Update__future__.pyand its docs to reflect this.(cherry picked from commit 0028c14)
Co-authored-by: YoSTEALTH [email protected]
https://bugs.python.org/issue41314