-
-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs claim from __future__ import annotations
will be on by default in 3.11
#92436
Labels
Comments
Relevant links:
|
JelleZijlstra
added a commit
to JelleZijlstra/cpython
that referenced
this issue
May 9, 2022
…_future__ import annotations"
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 12, 2022
…_future__ import annotations" (pythonGH-92568) (cherry picked from commit 6582c96) Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
JelleZijlstra
added a commit
that referenced
this issue
May 12, 2022
…e__ import annotations" (#92568)
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 12, 2022
…_future__ import annotations" (pythonGH-92568) (cherry picked from commit 6582c96) Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
JelleZijlstra
added a commit
to JelleZijlstra/cpython
that referenced
this issue
May 12, 2022
…from __future__ import annotations" (pythonGH-92568). (cherry picked from commit 6582c96) Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
JelleZijlstra
added a commit
that referenced
this issue
May 12, 2022
Seems like this was added in #92568 |
hello-adam
pushed a commit
to hello-adam/cpython
that referenced
this issue
Jun 2, 2022
…from __future__ import annotations" (pythonGH-92568). (python#92726) (cherry picked from commit 6582c96) Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://docs.python.org/3.11/library/__future__.html says the annotations
__future__
import is mandatory in 3.11, but it won't be. Right now, it's still undetermined whether this import will ever become the default; we may go with PEP-649's behavior or a combination of the two instead.In the docs, I think we should just say "To be determined". Optionally, we could add some discussion and link to the SC's pronouncements on the issue.
The text was updated successfully, but these errors were encountered: