Message249457
Doh, apparently I did once know about issue23726 and then forgot. Good catch.
Technically we could add a __class__ field to ModuleType directly, but I think then the ModuleType __class__ setter would basically need to be an exact reimplementation of everything that object_set_class already does? (Since it would still need to check that this particular ModuleType subclass was layout-compatible etc. -- e.g. no new __slots__.) And the end result would behave identically to the patch I just posted, except we'd replace a 2 line check in typeobject.c with some really complicated and bug-prone code in moduleobject.c? I don't think it buys us anything. |
|
Date |
User |
Action |
Args |
2015-09-01 06:41:57 | njs | set | recipients:
+ njs, lemburg, pitrou, larry, benjamin.peterson, Mark.Shannon, eltoder, serhiy.storchaka |
2015-09-01 06:41:56 | njs | set | messageid: <1441089716.95.0.302989264153.issue24912@psf.upfronthosting.co.za> |
2015-09-01 06:41:56 | njs | link | issue24912 messages |
2015-09-01 06:41:56 | njs | create | |
|