[Python-Dev] metaclass insanity (original) (raw)

Guido van Rossum guido@python.org
Wed, 30 Oct 2002 15:44:38 -0500

> The best thing to do would perhaps to make mro assignable, but > with a check that ensures the above constraint. I think I'd take a > patch for that.

Shouldn't be too hard. > I'd also take a patch for assignable bases. Note that there are > constraints between bases and base. Should assigning to bases automatically tweak mro and base? Guess so.

Yes. Note that changing base should not be done lightly -- basically, the old and new base must be layout compatible, exactly like for assignment to class.

What would assigning to base do in isolation? Perhaps that shouldn't be writeable.

Perhaps it could be writable when bases is a 1-tuple. But it's fine if it's not writable.

> I'd also take a patch for assignable name.

This is practically a one-liner, isn't it? Not hard, anyway.

Probably. Can't remember why I didn't do it earlier.

And there was me wondering what I was going to do this evening.

I don't have that problem -- a Zope customer problem was waiting for me today. :-(

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