Skip to content

gh-136843: Document how multiple inheritance works #136844

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

JelleZijlstra
Copy link
Member

@JelleZijlstra JelleZijlstra commented Jul 20, 2025

@rhettinger
Copy link
Contributor

This all looks good to me except for the final section about "solid bases". That last section should be checked by another reviewer with a stronger understanding of the details.

Copy link

@ilovelinux ilovelinux left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if it fits this PR but describing how super() works with multiple inheritance may be interesting!

@brianschubert
Copy link
Member

@ilovelinux super() follows the class' MRO. How lookups work in the presence of multiple inheritance is already documented (though if anything is unclear, suggestions are always welcome!). This issue is about documenting when multiple inheritance isn't possible to begin with.

@JelleZijlstra
Copy link
Member Author

The docs of super() already mention this: https://docs.python.org/3.14/library/functions.html#super

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting core review docs Documentation in the Doc dir skip news
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

4 participants