Fix docs: clarify variance behavior for PEP 695 generics#20971
Open
dhanusharer wants to merge 1 commit intopython:masterfrom
Open
Fix docs: clarify variance behavior for PEP 695 generics#20971dhanusharer wants to merge 1 commit intopython:masterfrom
dhanusharer wants to merge 1 commit intopython:masterfrom
Conversation
Author
|
I’ve opened a PR to clarify the variance behavior for PEP 695 generics in the documentation. |
dhanusharer
changed the title
dhanusharer
changed the title
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.
The documentation previously stated that user-defined generic classes
are invariant by default. This is true for the older TypeVar syntax,
but with the newer PEP 695 syntax (class MyCls[T]) type parameters
may be inferred as covariant when not used in invariant positions.
This PR updates the explanation in common_issues.rst to clarify this behavior.
Fixes #20366