➜

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 petr.viktorin
Recipients asvetlov, docs@python, martin.panter, petr.viktorin, vstinner
Date 2020-02-04.12:59:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1580821152.47.0.768313897624.issue16776@roundup.psfhosted.org>
In-reply-to
Content 
IMO, PyCFunction* should be a CPython-specific implementation detail: alternate implementations of the C-API don't need to support them, and extension authors should be fine without using them. (And if not, more efforts like PEP 590 Vectorcall should make it so.)

The functions are public in the sense that they don't have underscored names, but I wouldn't rush to make them documented.
History
Date User Action Args
2020-02-04 12:59:12petr.viktorinsetrecipients: + petr.viktorin, vstinner, asvetlov, docs@python, martin.panter
2020-02-04 12:59:12petr.viktorinsetmessageid: <1580821152.47.0.768313897624.issue16776@roundup.psfhosted.org>
2020-02-04 12:59:12petr.viktorinlinkissue16776 messages
2020-02-04 12:59:12petr.viktorincreate