[Python-Dev] perplexed by mro

Guido van Rossum guido@python.org
Fri, 04 Oct 2002 08:11:28 -0400


> > No, the whole point here is that the most inherited class's MRO
> > (i.e. z) can insert things in a base class's MRO.
> 
> It worries me that when I write a super call, I'll
> never be sure which method is going to be called,
> because someone might inherit me and mess with
> my mro.

But this is the whole *point* of the super() built-in.  Read up on
cooperative methods.

> But I can see that there are cases where this
> behaviour is desirable. I guess it's okay as long
> as I have the option of explicitly specifying
> the base class. (You're not going to take that
> away, are you?)

Not any time soon -- though I expect your fears are irrational. :-)

--Guido van Rossum (home page: http://www.python.org/~guido/)