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.
diff --git a/Misc/NEWS b/Misc/NEWS
index b3f3f93..bd8f51a 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -4,13 +4,11 @@
Type/class unification and new-style classes
-- Restrictions on multiple inheritance from classes with different
- metatypes have been relaxed. The only builtin metatypes are one for
- classic classes a second for new-style classes, so the primary
- visible effect is that this works now:
+- Multiple inheritance mixing new-style and classic classes in the
+ list of base classes is now allowed, so this works now:
class Classic: pass
- class Mixed(Classic, object): now
+ class Mixed(Classic, object): pass
The MRO (method resolution order) for each base class is respected
according to its kind, but the MRO for the derived class is computed