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 nikratio
Recipients docs@python, ncoghlan, nikratio, r.david.murray
Date 2013-07-01.02:19:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1372645157.97.0.747655652828.issue18334@psf.upfronthosting.co.za>
In-reply-to
Content
In that cases, maybe type(name, cls, clsdict) should actually raise an error if there's a metaclass with __prepare__ involved?

Presumably that would break only code that was already broken, but it would convert previously hidden behavioral bugs into an explicit expressions raised at the right point.
History
Date User Action Args
2013-07-01 02:19:18nikratiosetrecipients: + nikratio, ncoghlan, r.david.murray, docs@python
2013-07-01 02:19:17nikratiosetmessageid: <1372645157.97.0.747655652828.issue18334@psf.upfronthosting.co.za>
2013-07-01 02:19:17nikratiolinkissue18334 messages
2013-07-01 02:19:17nikratiocreate