Resolve forward references in generated init annotations - #1619
Open
Nikhi00718 wants to merge 2 commits into
Open
Resolve forward references in generated init annotations#1619Nikhi00718 wants to merge 2 commits into
Nikhi00718 wants to merge 2 commits into
Conversation
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.
Fixes #1596.
On Python 3.14, generated attrs initializers can lose access to forward references declared later in the defining module because their private globals dictionary is copied during decoration. This adds a lazy annotation provider that resolves generated initializer annotations against the defining module while preserving unresolved forward references. A regression test covers
inspect.signature(..., eval_str=True)andtyping.get_type_hints().Tests:
python -m pytest tests -q(1,408 passed, 4 skipped, 2 xfailed).