I stumbled across this extra, no-underscores mro method when I was using __metaclass__ = abc.ABCMeta. It seems to be the same as __mro__ except that it returns a list instead of a tuple. Here's a random example (ideone snippet):
import abc
import copy
class Life(object):
__metaclass__ = abc.ABCMeta
@abc.abstractmethod
def reproduce(self):
pass
class Bacterium(Life):
def reproduce(self):
return copy.deepcopy(self)
wiggly = Bacterium()
print wiggly.__class__.__mro__
# (, , )
print wiggly.__class__.mro()
# [, , ]
I found later that this isn't unique to ABCMeta but is available in all new-style classes.
So... why? What is this doing that __mro__ isn't?
解决方案This method can be overridden by a metaclass to customize the method resolution order for its instances. It is called at class instantiation, and its result is stored in __mro__.
Pretty self-explanatory to me...
mro() is called on instanciation and stores its result in __mro__. They don't really have the same purpose.