[Python-Dev] python and super (original) (raw)
Ricardo Kirkner ricardokirkner at gmail.com
Thu Apr 14 15:09:50 CEST 2011
- Previous message: [Python-Dev] cpython (merge default -> default): merge from push conflict.
- Next message: [Python-Dev] python and super
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi all,
I recently stumbled upon an issue with a class in the mro chain not calling super, therefore breaking the chain (ie, further base classes along the chain didn't get called). I understand it is currently a requirement that all classes that are part of the mro chain behave and always call super. My question is, shouldn't/wouldn't it be better, if python took ownership of that part, and ensured all classes get called, even if some class misbehaved?
For example, if using a stack-like structure, pushing super calls and popping until the stack was empty, couldn't this restriction be removed?
Thanks, Ricardo
- Previous message: [Python-Dev] cpython (merge default -> default): merge from push conflict.
- Next message: [Python-Dev] python and super
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]