-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
bpo-41314: fixed annotations __future__ version #21616
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
Conversation
cleaned up syntax and left `barry_as_FLUFL` as is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! This can be merged.
But please add a news item to make the last test pass. |
Misc/NEWS.d/next/Documentation/2020-07-25-14-20-00.bpo-41314.yrjko0.rst
Outdated
Show resolved
Hide resolved
Thanks @YoSTEALTH for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7, 3.8, 3.9. |
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]>
GH-21620 is a backport of this pull request to the 3.9 branch. |
GH-21621 is a backport of this pull request to the 3.8 branch. |
Sorry, @YoSTEALTH, I could not cleanly backport this to |
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]>
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]>
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]>
|
IIRC that particular buildbot is flaky and we can ignore it. |
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.
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.
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.
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.https://bugs.python.org/issue41314
Automerge-Triggered-By: @gvanrossum