-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
PEP 563 and annotations __future__ mandatory version #85486
Comments
In https://docs.python.org/3/library/__future__.html: In PEP-563: In Python *3.10* this will become the default behavior. Use of annotations incompatible with this PEP is no longer supported. Python 4.0 or 3.10? Not clear. |
The PEP was accepted apparently by Guido sometime after the second posting 21-Nov-2017. Guido added the annotations entry to __future__ on 1/26/2018 with the 'mandatory' version changed to 4.0, which means 'some indefinite undecided future version'. I consider '4.0' to the intentional and definitive until Guido or Lucasz say otherwise. When PEP implementations differ from the PEP, we do not usually go back and revise the PEP. The implementation rules unless clearly buggy. |
The PEP now says 3.10, so the docs for __future__ should be fixed. |
Ping? |
Waiting for someone to submit a PR. |
@ned This will need your assistance to merge the 3.7 backport IIUC. |
Never mind, Miss Islington failed to backport to 3.7, so let's forget about that. |
@gvanrossum I found couple of odd places where 4.0 is mentioned like https://docs.python.org/3/library/array.html for example, should a new issue be created? I am not sure how many more there are. |
In general, "4.0" means "never", and for some deprecations that seems totally appropriate. I wouldn't worry about it. I'm closing this issue now that all three PRs have been merged. Thanks for your contribution! |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: