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 NeilGirdhar
Recipients NeilGirdhar, docs@python, ncoghlan
Date 2016-10-15.17:56:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476554165.54.0.318433844064.issue28437@psf.upfronthosting.co.za>
In-reply-to
Content
"As a result of this, *both* implementations include a conditional check for a more derived metaclass in their namespace preparation logic, as well as an unconditional call to that metaclass derivation logic from type_new if the calculated metaclass is either type itself, or a subclass that calls up to super().__new__."

I don't see why that's necessary.  Either you should have the check in one place, or else have two equivalent checks.  Right now, the Python library is confusingly checking a subset of cases (when isinstance(meta, type)).  I suggest that you have the Python library check the entire set of cases so that the raised exception shows up in the right place.
History
Date User Action Args
2016-10-15 17:56:05NeilGirdharsetrecipients: + NeilGirdhar, ncoghlan, docs@python
2016-10-15 17:56:05NeilGirdharsetmessageid: <1476554165.54.0.318433844064.issue28437@psf.upfronthosting.co.za>
2016-10-15 17:56:05NeilGirdharlinkissue28437 messages
2016-10-15 17:56:05NeilGirdharcreate