diff options
| author | Guido van Rossum <guido@python.org> | 2001-11-15 20:27:54 (GMT) |
|---|---|---|
| committer | Guido van Rossum <guido@python.org> | 2001-11-15 20:27:54 (GMT) |
| commit | 3d27df07344039a5fdd741194dfb9c0a3a11a091 (patch) | |
| tree | 8146f2e3176e2a80076aee577a7cfa096decddf8 | |
| parent | 76f7fe37bb058647d4c8475a921abbd20b8c2d47 (diff) | |
| download | cpython-3d27df07344039a5fdd741194dfb9c0a3a11a091.zip cpython-3d27df07344039a5fdd741194dfb9c0a3a11a091.tar.gz cpython-3d27df07344039a5fdd741194dfb9c0a3a11a091.tar.bz2 | |
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.
| -rw-r--r-- | Misc/NEWS | 8 |
1 files changed, 3 insertions, 5 deletions
@@ -4,13 +4,11 @@ Release date: 16-Nov-2001 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 |