Repository navigation
__future__.annotations has inaccurate mandatoryRelease value #93626
Description
Activity
PEP 563 has been deferred. There will be no behavior changes around the future import in 3.11. See https://docs.python.org/3.10/library/__future__.html#id1
Lines 145 to 147 in 68f6a5d
Does this need to be updated then? All the 3.11 releases so far have
annotationsturned on.Maybe the 'What's New' could mention that it has been delayed again.
could it be set to
Noneinstead?Lines 35 to 36 in f4c0348
the wording could be changed to say:
MandatoryRelease may also be None, meaning that a planned feature has
no predicted release or has been dropped.Reacted by KotlinIslandI've made that change.
- changed the title
[-]3.11 What's new doesn't mention `future.__annotations__` becoming active[/-][+]`future.__annotations__` is active in 3.11 betas[/+]on Jun 29, 2022 @JelleZijlstra Could this be reopened?
Imho this is a release blocker
Reacted by KotlinIsland- changed the title
[-]`future.__annotations__` is active in 3.11 betas[/-][+]`__future__.annotations` has inaccurate `mandatoryRelease` value[/+]on Jun 30, 2022 I see no need for this to block beta 4, but it should be resolved before final release.
/cc @pablogsal
Reacted by Thomas Grainger
future.__annotations__has been postponed, yet it is active in the 3.11 betas.__future__.annotationstoNone#93628>A clear and concise description of the issue.
https://docs.python.org/3.11/whatsnew/3.11.html
This page doesn't mention pep 563 at all.