[issue41475] __future__.annotations set to become default in Python 4.0?

YoSTEALTH added the comment: @cool-RR since your patch focuses on ``3.7`` there might be a merge issue. There might be other place where ``4.0`` is mentioned though. Its better to let core dev like Raymond make the call. -- ___ Python tracker

[issue41475] __future__.annotations set to become default in Python 4.0?

Ram Rachum added the comment: Thanks for linking that, YoStealth. Unless I'm missing anything, it looks like there's agreement that the right answer is 3.10, and my PR fixes a spot which was omitted in the PR from the previous issues. Agreed? --

[issue41475] __future__.annotations set to become default in Python 4.0?

YoSTEALTH added the comment: @rhettinger https://bugs.python.org/issue41314 -- nosy: +YoSTEALTH ___ Python tracker ___ ___

[issue41475] __future__.annotations set to become default in Python 4.0?

Raymond Hettinger added the comment: Keep it focused one place — there's no benefit to multiple tracker entries and/or multiple PRs. Do look to see all the places that would be need to be updated. Also, let Łukasz reply — this was his PEP. Also, I'm not sure that we're backporting anything

[issue41475] __future__.annotations set to become default in Python 4.0?

Ram Rachum added the comment: If you'd like me to patch that too, let me know. Also, I'll need a decision on whether it should be on a separate PR and if so, to which versions it should be backported. -- ___ Python tracker

[issue41475] __future__.annotations set to become default in Python 4.0?

Raymond Hettinger added the comment: $ python3.9 Python 3.9.0b4 (v3.9.0b4:69dec9c8d2, Jul 2 2020, 18:41:53) [Clang 6.0 (clang-600.0.57)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from __future__ import annotations >>> annotations _Feature((3, 7, 0,