Make from __future__ import annotations the default in Python 3.10#1371
Merged
Conversation
Member
|
I suggest to discuss that at: https://bugs.python.org/issue38605 |
d078f4b to
c82ed2b
Compare
from __future__ import annotations the default in Python 3.9from __future__ import annotations the default in Python 3.10
AA-Turner
pushed a commit
to AA-Turner/peps
that referenced
this pull request
Aug 15, 2020
mnm678
pushed a commit
to mnm678/peps
that referenced
this pull request
Oct 22, 2020
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.
The Language Summit discussion suggests this should be flipped either in Python 3.9 or in Python 3.10. An informal poll ran at the event with 33 votes has shown that 65% would like to see the change in 3.9, 29% in 3.10, 3% in 4.0, and 3% "never" :-)
This PR is open to gather feedback from those concerned.
Side note: The previously documented policy of raising deprecation warnings if there's any annotation was unrealistic. It would raise huge numbers of warnings, a lot of them in third-party code that the receiver of the warning can do nothing about. That part we need to remove from the document anyway.