Message266654
Yes, that would be preferable. The error message is at Objects/typeobject.c#l2301, but keep in mind that this message is shown for both faulty calls to type() as well as any of its subclasses that don't override __new__, and I'm lukewarm on adding e.g. a PyType_Check call before that; might as well replace the PyType_CheckExact call and make this work. I'm not knowledgeable enough in that field though, you'll need a core dev's advice. |
|
Date |
User |
Action |
Args |
2016-05-30 00:39:08 | abarry | set | recipients:
+ abarry, ppperry |
2016-05-30 00:39:08 | abarry | set | messageid: <1464568748.58.0.282100506486.issue27157@psf.upfronthosting.co.za> |
2016-05-30 00:39:08 | abarry | link | issue27157 messages |
2016-05-30 00:39:07 | abarry | create | |
|