Message345889
The problem is that __module__ is deduced from the caller's frame in type.__new__(). In case if type.__new__() is called directly, __module__ is set to the name of the module where type.__new__() is called. So virtually every type subclass which defines the __new__ method and calls type.__new__() inside it starves from the same issue.
It can be fixed in general if deduce __module__ in type.__call__() instead of type.__new__(). |
|
Date |
User |
Action |
Args |
2019-06-17 19:02:13 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, steven.daprano, levkivskyi, abarry, alegonz |
2019-06-17 19:02:13 | serhiy.storchaka | set | messageid: <1560798133.19.0.103113944828.issue28869@roundup.psfhosted.org> |
2019-06-17 19:02:13 | serhiy.storchaka | link | issue28869 messages |
2019-06-17 19:02:13 | serhiy.storchaka | create | |
|