This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author jdemeyer
Recipients docs@python, jdemeyer, rhettinger, steven.daprano
Date 2019-06-07.09:57:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1559901431.74.0.0354897681455.issue37176@roundup.psfhosted.org>
In-reply-to
Content
> Only one of the two arguments is called "type". The other is called 
"object-or-type".

I'm having problems with the first word of "a parent or sibling class of type". The most important part of super() is to *which* class that attribute lookups are delegated to and this is not explained.

> The __mro__ attribute is on the type, not the instance:

Sorry for that. I meant to say:

And the sentence "The __mro__ attribute of the type lists the method resolution search order used by both getattr() and super()" is even wrong or at least confusing: what matters is not the MRO of the type (the first argument to super()) but the MRO of ***the type of*** the object (the second argument to super()).

> Yes it is. Look at the example given:

An example is not an explanation. But it's true, this is the least of my problems with this doc.
History
Date User Action Args
2019-06-07 09:57:11jdemeyersetrecipients: + jdemeyer, rhettinger, steven.daprano, docs@python
2019-06-07 09:57:11jdemeyersetmessageid: <1559901431.74.0.0354897681455.issue37176@roundup.psfhosted.org>
2019-06-07 09:57:11jdemeyerlinkissue37176 messages
2019-06-07 09:57:11jdemeyercreate