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 docs@python, ncoghlan, nikratio, r.david.murray
Date 2013-07-01.07:35:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372664131.9.0.919052520477.issue18334@psf.upfronthosting.co.za>
In-reply-to
Content
Unfortunately, it's not that simple, as calling type(name, bases, namespace) is *exactly* what a subclass will do as part of creating the type object.

From inside the type implementation, we can't tell the difference between "properly called from the child type" and "improperly called without preparing the namespace first".
History
Date User Action Args
2013-07-01 07:35:31ncoghlansetrecipients: + ncoghlan, r.david.murray, nikratio, docs@python
2013-07-01 07:35:31ncoghlansetmessageid: <1372664131.9.0.919052520477.issue18334@psf.upfronthosting.co.za>
2013-07-01 07:35:31ncoghlanlinkissue18334 messages
2013-07-01 07:35:31ncoghlancreate