Skip to content

gh-99505: Fix docs for determining the metaclass #123349

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 3 commits into
base: main
Choose a base branch
from

Conversation

robsdedude
Copy link

@robsdedude robsdedude commented Aug 26, 2024

Alternatively, this could be less explicit but more prose by adding something along the lines of

Further, must the metaclass always be valid when removing any number of
right-most bases.

to the paragraph about the TypeError. However, I find it really hard to wrap my head around the rules if they're written in prose like that as the metaclass selection process is not necessarily super straight forward.

Closes #99505


📚 Documentation preview 📚: https://cpython-previews--123349.org.readthedocs.build/

@ghost
Copy link

ghost commented Aug 26, 2024

All commit authors signed the Contributor License Agreement.
CLA signed

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

Successfully merging this pull request may close these issues.

Resolution / determining of metaclass docs don't align with what really happens
1 participant