Understanding the MRO with multiple inheritance

Chris Angelico rosuav at gmail.com
Sat Mar 30 05:07:24 EDT 2019


On Sat, Mar 30, 2019 at 7:08 PM Arup Rakshit <ar at zeit.io> wrote:
>
> Thanks Chris and Dieter. I think I got it. It seems it follows the __mro__ of the caller class, not the current class __mro_.

That is correct. It is the object that has an MRO, and it's that
object's MRO that matters to super.

ChrisA



More information about the Python-list mailing list