fix: do not treat overridden methods as inherited when mixing a generic base with a plain base#887
Open
SAY-5 wants to merge 2 commits into
Open
fix: do not treat overridden methods as inherited when mixing a generic base with a plain base#887SAY-5 wants to merge 2 commits into
SAY-5 wants to merge 2 commits into
Conversation
…ic base with a plain base
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.
When a class inherits from both a
Generic[...]base and a plain base class,Class._basesprepended the plain base from__orig_bases__ahead of the class itself in__mro__, causing overridden methods to be reported as inherited (and their docstrings dropped). The fix only prepends__orig_bases__entries that are absent from__mro__, which still covers the TypedDict case. Closes #862.