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 eric.snow
Recipients Mark.Shannon, eric.snow, gvanrossum, mattip, nascheme, petr.viktorin, vstinner
Date 2021-03-17.14:40:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> I am confused. How can widening the usable number of functions (i.e. using
> the whole C-API rather than the limited API) help c-extension modules be
> usable in subinterpreters? Aren't the same singletons, exception types, and
> other types exposed in the full C-API?

If Py_LIMITED_API is defined then things would stay the same.  Otherwise we would replace the names with macros to do the appropriate lookup.  (That isn't the whole story since the Py*_Type names are PyTypeObject and not PyObject*.)
Date User Action Args
2021-03-17 14:40:20eric.snowsetrecipients: + eric.snow, gvanrossum, nascheme, vstinner, petr.viktorin, Mark.Shannon, mattip
2021-03-17 14:40:20eric.snowsetmessageid: <>
2021-03-17 14:40:20eric.snowlinkissue43503 messages
2021-03-17 14:40:20eric.snowcreate