转自:http://xiaocong.github.io/blog/2012/06/13/python-mixin-and-mro/
In object-oriented programming languages, a mixin is a class that provides a certain functionality to be inherited or just reused by a subclass, while not meant for instantiation (the generation of objects of that class). Mixins are synonymous with abstract base classes. Inheriting from a mixin is not a form of specialization but is rather a means of collecting functionality. A class or object may “inherit” most or all of its functionality from one or more mixins, therefore mixins can be thought of as a mechanism of multiple inheritance.
Wikipedia Mixin
简单的说, mixin 是一种类的多继承的机制.
就如stackoveflow 上的回答, 有两个主要的使用 mixin 的场景:
例如, werkzeug 的request
, response
系统. 我们可以实现简单request
如下:
1 2 3 4 |
|
如果我们希望支持accept header
, 可以这样实现:
1 2 3 4 |
|
如果我们希望request
对象支持accept header
, etags
, authentication
, user agent
, 可以这样实现:
1 2 3 4 |
|
假定我们有下面两个类需要mixin:
1 2 3 4 5 |
|
1 2 |
|
1 2 3 4 5 6 7 |
|
type
动态构造类来实现 Mixin 1
|
|
__bases__
来实现 Mixin. 只能 mixin classic class
1 2 3 4 5 6 7 |
|
In object-oriented programming languages with multiple inheritance, the diamond problem (sometimes referred to as the “deadly diamond of death”) is an ambiguity that arises when two classes B and C inherit from A, and class D inherits from both B and C. If D calls a method defined in A (and does not override the method), and B and C have overridden that method differently, then from which class does it inherit: B, or C?
Wikipedia Diamond Problem
多继承时, 运行环境必须知道调用哪一个父类的方法. Python2.3开始采用C3
方法解析顺序(Method Resolution Order, 简称MRO)来动态解析调用的方法.
1 2 3 4 5 6 7 8 9 |
|
参照上面代码执行的结果, 我们可以看出, class X
的 MRO 是 <class '__main__.X'>, <class '__main__.A'>, <class '__main__.B'>, <type 'object'>
. 当我们调用X
实例对象的某个方法, 运行环境会按照X, A, B, object
顺序解析该方法. 越左边的越优先, 也就是说如果只有A
,B
定义了这个方法, 系统会选择最先解析到的方法, 也就是A
的方法定义. 同样, class Y
的 MRO 是 <class '__main__.Y'>, <class '__main__.B'>, <class '__main__.A'>, <type 'object'>
, 对于Y
来说, B
的方法要优先于A
进行解析.
上面定义的类X
和Y
对A
和B
的方法解析顺序是刚好相反的, 如果有一个类继承于X
和Y
会出现什么结果?
1 2 3 4 5 6 |
|
上面的错误说明, 类的继承必须保持一致的 MRO. 由于基类X
和Y
的 MRO 有冲突, 因此我们不可能从X
和Y
继承另外一个类.
关于 MRO 的算法可以参考官网上的Python 2.3 方法解析顺序.