Peter Otten wrote:
> The problem with that aren't incompatible signatures, but the lack of
an
> implementation of the reset() method at the top of the diamond-shaped
> inheritance graph that does _not_ call the superclass method. That
method
> could be basically a noop:
Ok, now that's cool! Up
[EMAIL PROTECTED] wrote:
> What if I want to call other methods as well? Modifying your example a
> bit, I'd like the reset() method call of Child to invoke both the
> Mother and Father reset() methods, without referencing them by name,
> i.e., Mother.reset(self).
[example snipped]
The problem w
