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 WildCard65
Recipients WildCard65
Date 2020-06-30.15:34:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1593531275.14.0.931108904355.issue41171@roundup.psfhosted.org>
In-reply-to
Content
The current goal from what I can tell for Python is to have all C based modules move away from static types and instead use "PyType_FromSpec" and the variant that specifies base classes.

The only problem is, PyType_FromSpec and it's variant makes the assumption the caller wants "PyType_Type" as the type's metaclass.

Why not add companion methods to them prefixed with "PyMetaType" and have the "PyType" ones internally invoke these new methods with "PyType_Type" as the metaclass (to keep existing behavior and backwards compatibility)
History
Date User Action Args
2020-06-30 15:34:35WildCard65setrecipients: + WildCard65
2020-06-30 15:34:35WildCard65setmessageid: <1593531275.14.0.931108904355.issue41171@roundup.psfhosted.org>
2020-06-30 15:34:35WildCard65linkissue41171 messages
2020-06-30 15:34:35WildCard65create