gh-149985: Remove future annotations and if TYPE_CHECKING in pyrepl - #149992
Merged
Conversation
…repl `from __future__ import annotations` is soft-deprecated now that evaluation of annotations is always deferred. `if TYPE_CHECKING` can often be replaced with lazy imports.
JelleZijlstra
marked this pull request as ready for review
May 18, 2026 14:11
JelleZijlstra
requested review from
ambv,
lysnikolaou and
pablogsal
as code owners
May 18, 2026 14:11
|
This PR is stale because it has been open for 90 days with no activity. |
github-actions
Bot
removed
the
stale
clin1234
pushed a commit
to clin1234/cpython
that referenced
this pull request
Aug 27, 2026
…repl (python#149992) `from __future__ import annotations` is soft-deprecated now that evaluation of annotations is always deferred. `if TYPE_CHECKING` can often be replaced with lazy imports.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
from __future__ import annotationsis soft-deprecated now that evaluationof annotations is always deferred.
if TYPE_CHECKINGcan often be replacedwith lazy imports.
A risk is that creation of dataclasses will be slower without
from __future__ import annotations, because the dataclass machinery will force evaluation of annotations. However, if the annotations are simple my simple benchmarks do not show an appreciable slowdown.