[issue41314] PEP 563 and annotations __future__ mandatory version

Guido van Rossum added the comment: 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! -- resolution: -> fixed stage: patc

[issue41314] PEP 563 and annotations __future__ mandatory version

miss-islington added the comment: New changeset fdc91c2e6096f60ddb8b7f72fe7926ccbbf42800 by Miss Islington (bot) in branch '3.9': bpo-41314: fixed annotations __future__ version (GH-21616) https://github.com/python/cpython/commit/fdc91c2e6096f60ddb8b7f72fe7926ccbbf42800 --

[issue41314] PEP 563 and annotations __future__ mandatory version

miss-islington added the comment: New changeset b99f770230e0db390aa80c5135b1053f3be48e19 by Miss Islington (bot) in branch '3.8': bpo-41314: fixed annotations __future__ version (GH-21616) https://github.com/python/cpython/commit/b99f770230e0db390aa80c5135b1053f3be48e19 --

[issue41314] PEP 563 and annotations __future__ mandatory version

YoSTEALTH added the comment: @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. -- ___ Python tracker

[issue41314] PEP 563 and annotations __future__ mandatory version

Guido van Rossum added the comment: Never mind, Miss Islington failed to backport to 3.7, so let's forget about that. -- versions: -Python 3.7 ___ Python tracker ___ ___

[issue41314] PEP 563 and annotations __future__ mandatory version

Guido van Rossum added the comment: @ned This will need your assistance to merge the 3.7 backport IIUC. -- nosy: +ned.deily ___ Python tracker ___

[issue41314] PEP 563 and annotations __future__ mandatory version

miss-islington added the comment: New changeset 0028c14073109595e7532ec00bb1e8bf39ecfb4d by YoSTEALTH in branch 'master': bpo-41314: fixed annotations __future__ version (GH-21616) https://github.com/python/cpython/commit/0028c14073109595e7532ec00bb1e8bf39ecfb4d -- nosy: +miss-islin

[issue41314] PEP 563 and annotations __future__ mandatory version

Change by miss-islington : -- pull_requests: +20762 pull_request: https://github.com/python/cpython/pull/21621 ___ Python tracker ___ __

[issue41314] PEP 563 and annotations __future__ mandatory version

Change by miss-islington : -- pull_requests: +20761 pull_request: https://github.com/python/cpython/pull/21620 ___ Python tracker ___ __

[issue41314] PEP 563 and annotations __future__ mandatory version

Change by YoSTEALTH : -- versions: +Python 3.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue41314] PEP 563 and annotations __future__ mandatory version

Change by YoSTEALTH : -- keywords: +patch nosy: +YoSTEALTH nosy_count: 5.0 -> 6.0 pull_requests: +20758 stage: resolved -> patch review pull_request: https://github.com/python/cpython/pull/21616 ___ Python tracker

[issue41314] PEP 563 and annotations __future__ mandatory version

Guido van Rossum added the comment: Waiting for someone to submit a PR. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue41314] PEP 563 and annotations __future__ mandatory version

wyz23x2 added the comment: Ping? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/

[issue41314] PEP 563 and annotations __future__ mandatory version

Guido van Rossum added the comment: The PEP now says 3.10, so the docs for __future__ should be fixed. -- resolution: not a bug -> status: closed -> open ___ Python tracker _

[issue41314] PEP 563 and annotations __future__ mandatory version

Terry J. Reedy added the comment: 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 cons