I m pretty much new in Python object oriented programming and I have trouble
understanding the super() function (new style classes) especially when it comes to multiple inheritance.
For example if you have something like:
class First(object):
def __init__(self):
print "first"
class Second(object):
def __init__(self):
print "second"
class Third(First, Second):
def __init__(self):
super(Third, self).__init__()
print "that s it"
What I don t get is: will the Third() class inherit both constructor methods? If yes, then which one will be run with super() and why?
http://en.wikipedia.org/wiki/C3_linearization
http://en.wikipedia.org/wiki/C3_linearization
http://python-history.blogspot.com/2010/06/method-resolution-order.html
http://python-history.blogspot.com/2010/06/method-resolution-order.html
But, briefly: in your example, Third() will call First.__init__. For such simple situations, Python will look for the attribute (in this case, __init__) on the class s parents, left to right. So, if you define
class Third(First, Second):
...
Python will look at First, and, if First doesn t have the attribute, at Second.
This situation becomes more complex when inheritance starts crossing paths (say, if First inherited from Second, for instance). Read the link above for more details, but, in a nutshell, Python will try to maintain the order in which each class appears on the inheritance list, child classes first.
So, for instance, if you had:
class First(object):
def __init__(self):
print "first"
class Second(First):
def __init__(self):
print "second"
class Third(First):
def __init__(self):
print "third"
class Fourth(Second, Third):
def __init__(self):
super(Fourth, self).__init__()
print "that s it"
the MRO would be [Fourth, Second, Third, First].
By the way: if Python cannot find a coherent method resolution order, it ll raise an exception, instead of falling back to a behaviour which might surprise the user.
Edited to add example of an ambiguous MRO:
class First(object):
def __init__(self):
print "first"
class Second(First):
def __init__(self):
print "second"
class Third(First, Second):
def __init__(self):
print "third"
Should Third s MRO be [First, Second] or [Second, First]? There s no obvious expectation, and Python will raise an error:
TypeError: Error when calling the
metaclass bases
Cannot create a consistent method resolution order (MRO) for bases
Second, First
[Edit] I see several people arguing that the examples above lack super() calls, so let me explain: the point of the examples is to show how the MRO is constructed. They are not intended print "first
second hird" or whatever. You can - and should, of course, play around with the example, add super() calls, see what happens, and gain a deeper understanding of Python s inheritance model. But my goal here is to keep it simple and show how the MRO is build. And it is built as I explained:
>>> Fourth.__mro__
(<class __main__.Fourth >, <class __main__.Second >, <class __main__.Third >, <class __main__.First >, <type object >)
http://stackoverflow.com/questions/3277367/how-does-pythons-super-work-with-multiple-inheritance