This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients daniel.urban, ezio.melotti, flox, ncoghlan
Date 2013-02-17.11:50:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Ah, I think I see your point - because __init_class__ is supposed to be a class method on instances of the metaclass, the anchor needs to be on object (the highest level instance of the default metaclass), not on type if we don't want super to behave strangely?

I think that's a valid conclusion (albeit a very subtle difference relative to an ordinary method on type), and compared to the tapdancing we do in __new__ and __init__ to help them be valid anchors for cooperative multiple inheritance, adding object.__init_class__ is a relatively minor thing.

If you wanted to propose a patch to the PEP as well, that would be great.
Date User Action Args
2013-02-17 11:50:24ncoghlansetrecipients: + ncoghlan, ezio.melotti, flox, daniel.urban
2013-02-17 11:50:24ncoghlansetmessageid: <>
2013-02-17 11:50:24ncoghlanlinkissue17044 messages
2013-02-17 11:50:23ncoghlancreate