bpo-38605: Update "Future statements" docs since PEP 563 is always enabled #25236
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
isidentical
approved these changes
Apr 7, 2021
pablogsal
added a commit
to pablogsal/cpython
that referenced
this pull request
Apr 20, 2021
…lways enabled (pythonGH-25236)" This reverts commit 1be456a.
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.
Update documentation section for "Future statements" to reflect that
from __future__ import annotationsis on by default, and no features require using the future statement now.https://bugs.python.org/issue38605
Automerge-Triggered-By: GH:isidentical