Repository navigation
__future__.annotations has inaccurate mandatoryRelease value #93626
Description
future.__annotations__ has been postponed, yet it is active in the 3.11 betas.
>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.
Activity
JelleZijlstra commentedon Jun 9, 2022
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
KotlinIsland commentedon Jun 9, 2022
cpython/Lib/__future__.py
Lines 145 to 147 in 68f6a5d
Does this need to be updated then? All the 3.11 releases so far have
annotationsturned on.KotlinIsland commentedon Jun 9, 2022
Maybe the 'What's New' could mention that it has been delayed again.
graingert commentedon Jun 18, 2022
could it be set to
Noneinstead?cpython/Lib/__future__.py
Lines 35 to 36 in f4c0348
the wording could be changed to say:
KotlinIsland commentedon Jun 19, 2022
I've made that change.
[-]3.11 What's new doesn't mention `future.__annotations__` becoming active[/-][+]`future.__annotations__` is active in 3.11 betas[/+]KotlinIsland commentedon Jun 29, 2022
@JelleZijlstra Could this be reopened?
graingert commentedon Jun 29, 2022
Imho this is a release blocker
[-]`future.__annotations__` is active in 3.11 betas[/-][+]`__future__.annotations` has inaccurate `mandatoryRelease` value[/+]zware commentedon Jun 30, 2022
I see no need for this to block beta 4, but it should be resolved before final release.
/cc @pablogsal
pythongh-93626: Set the release for `__future__.annotations` to `None` (
gh-93626: Set the release for `__future__.annotations` to `None` (GH-…
gh-93626: Set the release for `__future__.annotations` to `None` (GH-…