forked from python/peps
-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Description
I am planning to write a PEP focused on how to implement and ship PEP 649. This PEP will include some changes and additions to the behavior specified in PEP 649 itself.
Topics to cover:
- Transition plan: what happens to
from __future__ import annotations? (Current leaning: keep it around until 3.13 reaches EOL, then deprecate it and remove it two years later.) - REPL behavior change (https://discuss.python.org/t/pep-649-behavior-of-the-repl/54109)
- New
annotationsmodule (https://discuss.python.org/t/pep-649-deferred-evaluation-of-annotations-tentatively-accepted/21331/69) - Enum for annotation format? (gh-119180: PEP 649 compiler changes python/cpython#119361 (comment))
- Revisit "set
__annotate__to None"? (gh-119180: PEP 649: Add __annotate__ attributes python/cpython#119209 (review)) - Remove the suggested flag on code objects to mark if they can be evaluated with the special execution environment?
- Specify behavior for annotations on classmethod and staticmethod
- Add
typing.evaluate_forward_ref? Combines evaluating the ForwardRef with typing-specific conversions (typing._type_check). - Specify mechanism for FORWARDREF/SOURCE evaluation of TypeVar bounds etc.
I'm going to hold off on writing the PEP until someone adds PEP 748, so I can get PEP 749 :)
AlexWaygood and carljm
Metadata
Metadata
Assignees
Labels
No labels