RetroSearch Browse

Thu Apr 14 15:15:10 CEST 2011 · https://mail.python.org/pipermail/python-dev/2011-April/110687.html

2011/4/14 Ricardo Kirkner <ricardokirkner at gmail.com>:
> 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?

No. See line 2 of the Zen of Python.

-- 
Regards,
Benjamin

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2011-April/110687.html below:

[Python-Dev] python and super