3 ms·
I disagree, that's extremely fragile. It might work for the particular class you are implementing. However, it might cause subclasses of that class to break,
by Peristarkawan 15y ago
I disagree, that's extremely fragile. It might work for the particular class you are implementing. However, it might cause subclasses of that class to break, since those subclasses will have a different MRO than the current class, and you could end up skipping more of the MRO than you intended.
- deleted 15y ago[deleted]
- jessedhillon 15y agoHow would it cause a subclass to break? The ancestor is explicitly specified -- this could only break if the MRO was modified to exclude that particular ancestor.