[issue3453] PyType_Ready doesn't ensure that all bases are ready
Roger Upole
report at bugs.python.org
Tue Aug 19 22:58:05 CEST 2008
Roger Upole <rupole at hotmail.com> added the comment:
This doesn't address the discrepancy between tp_base and tp_bases.
If multiple bases are used, it's no longer 'good practice', it's an
absolute requirement. IMO, it should call PyType_Ready for all bases,
or none of them.
Since the code assumes that all bases have been
initialized, it could at least ASSERT so, rather than crashing deep
within the mro calculations.
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue3453>
_______________________________________
More information about the Python-bugs-list
mailing list