Fix TypeError with evaluate_forward_ref on some 3.10 and 3.9 versions - #558
Merged
JelleZijlstra merged 4 commits intoApr 1, 2025
Merged
JelleZijlstra merged 4 commits into
JelleZijlstra merged 4 commits into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
JelleZijlstra
approved these changes
Apr 1, 2025
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
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.
The allow_special_forms keyword was not introduced together with __forward_is_class__ in 3.10.1 and 3.9.8, but later. This PR corrects the version range.