Re:Wield Python's super() like a Jedi
by Peristarkawan on Thursday May 26, 2011 @02:35PM
(#2588908)
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.
I think in a case like the one you describe, where the direct ancestor's implementation is circumvented to access a different ancestor's implementation, it should be done by calling
That should improve understanding.