➜

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 eryksun
Recipients abarry, eryksun, gvanrossum, ppperry, r.david.murray, rhettinger, serhiy.storchaka, steven.daprano
Date 2016-05-30.17:23:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1464629022.51.0.277958806273.issue27157@psf.upfronthosting.co.za>
In-reply-to
Content 
> Please treat this as a new feature (just in case) and only 
> apply it to 3.6.

How about changing PyType_CheckExact to PyType_Check for 2.7 and 3.5? It solves the original problem by expanding the single-argument case to metaclasses that aren't an exact instance of `type`. I think that's unlikely to break existing code. It also shouldn't cause a performance problem since the PyType_Check macro uses the Py_TPFLAGS_TYPE_SUBCLASS flag.
History
Date User Action Args
2016-05-30 17:31:19eryksununlinkissue27157 messages
2016-05-30 17:23:42eryksunsetrecipients: + eryksun, gvanrossum, rhettinger, steven.daprano, r.david.murray, serhiy.storchaka, ppperry, abarry
2016-05-30 17:23:42eryksunsetmessageid: <1464629022.51.0.277958806273.issue27157@psf.upfronthosting.co.za>
2016-05-30 17:23:42eryksunlinkissue27157 messages
2016-05-30 17:23:42eryksuncreate