Use Generator TypeVar defaults #18384
Merged
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
cdce8p
commented
Dec 30, 2024
| def enter_subpattern(self, subject: Value) -> Generator[None, None, None]: | ||
| def enter_subpattern(self, subject: Value) -> Generator[None]: |
There was a problem hiding this comment.
#18382 also adds `from future import annotations. Including it here would just create a merge conflict and isn't strictly necessary anyway.
hauntsaninja
approved these changes
Dec 30, 2024
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.
collections.abc.Generatordoesn't check the number of TypeVars (in contrast totyping.Generator). So it's possible to useGenerator[None]even for Python 3.9.