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 NeilGirdhar, docs@python, ncoghlan
Date 2016-10-16.07:45:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1476603935.75.0.438679158092.issue28437@psf.upfronthosting.co.za>
In-reply-to
Content
Oops, couple of typos:

"... only triggers metaclass resolution at that point ..."

"... if either the metaclass being instantiated is a subclass of all the metaclasses of all of the bases ..."

But the only way to bypass the "most derived metaclass" rule is for the the metaclass hint to be a callable that creates something that *isn't* a subclass of type. If you look at the tracebacks you're getting, you should see that the failure *isn't* in the class statement or the outer dynamic type, it's in "metaclass_callable", where the *inner* dynamic type creation is failing.
History
Date User Action Args
2016-10-16 07:45:35ncoghlansetrecipients: + ncoghlan, docs@python, NeilGirdhar
2016-10-16 07:45:35ncoghlansetmessageid: <1476603935.75.0.438679158092.issue28437@psf.upfronthosting.co.za>
2016-10-16 07:45:35ncoghlanlinkissue28437 messages
2016-10-16 07:45:35ncoghlancreate