This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients lukasz.langa, vstinner
Date 2019-10-27.16:07:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>
In-reply-to
Content
The PEP 563: Postponed evaluation of annotations was introduced an opt-in feature using "from __future__ import annotations". It is scheduled to become the default in Python 4.0.

I would prefer to limit the number of incompatible changes in Python 4.0: it should just a "regular" release, with a regular number of incompatible changes. The version number change is going to cause enough troubles...

Would it be possible possible to enable postponed evaluation of annotations either before or after Python 4.0? For example, can we imagine to enable it by default in Python 3.9? If not, what about Python 3.10?

See also the PEP 608 (Coordinated Python release) and bpo-38604 (Schedule Py_UNICODE API removal).
History
Date User Action Args
2019-10-27 16:07:10vstinnersetrecipients: + vstinner, lukasz.langa
2019-10-27 16:07:10vstinnersetmessageid: <1572192430.43.0.755831692199.issue38605@roundup.psfhosted.org>
2019-10-27 16:07:10vstinnerlinkissue38605 messages
2019-10-27 16:07:10vstinnercreate