Commit 3d27df07 authored by Guido van Rossum's avatar Guido van Rossum

Correct the description of mixed multiple inheritance: the code

special-cases classic classes, it doesn't do anything about other
cases where different metaclasses are involved (except for the trivial
case where one metaclass is a subclass of the others).  Also note that
it's metaclass, not metatype.
parent 76f7fe37
...@@ -4,13 +4,11 @@ Release date: 16-Nov-2001 ...@@ -4,13 +4,11 @@ Release date: 16-Nov-2001
Type/class unification and new-style classes Type/class unification and new-style classes
- Restrictions on multiple inheritance from classes with different - Multiple inheritance mixing new-style and classic classes in the
metatypes have been relaxed. The only builtin metatypes are one for list of base classes is now allowed, so this works now:
classic classes a second for new-style classes, so the primary
visible effect is that this works now:
class Classic: pass class Classic: pass
class Mixed(Classic, object): now class Mixed(Classic, object): pass
The MRO (method resolution order) for each base class is respected The MRO (method resolution order) for each base class is respected
according to its kind, but the MRO for the derived class is computed according to its kind, but the MRO for the derived class is computed
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment