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 serhiy.storchaka
Recipients abarry, alegonz, levkivskyi, serhiy.storchaka, steven.daprano
Date 2019-06-17.19:02:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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:13serhiy.storchakasetrecipients: + serhiy.storchaka, steven.daprano, levkivskyi, abarry, alegonz
2019-06-17 19:02:13serhiy.storchakasetmessageid: <>
2019-06-17 19:02:13serhiy.storchakalinkissue28869 messages
2019-06-17 19:02:13serhiy.storchakacreate