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 jwuttke
Recipients jdemeyer, jwuttke
Date 2020-10-28.14:18:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1603894711.43.0.142721480752.issue42181@roundup.psfhosted.org>
In-reply-to
Content
The current 3.9 docs do not describe PyEval_CallObjectWithKeywords, among other PyEval_CallObject* functions.

Yes, I know, these functions are deprecated. But they are still part of the API; they ought to be documented.

Rather, given that they are deprecated, there is more need than ever to document them: The documentation should specify when they have been deprecated, until then they are guaranteed to be supported, and most importantly, how they are to be replaced.

Fulltext search leads me to the 3.9 Changelog that says: »PyEval_CallFunction, PyEval_CallMethod and PyEval_CallObjectWithKeywords are deprecated. Use PyObject_Call() and its variants instead.« This is far not enough. As a maintainer of 3rd-party code with no knowledge of and no interest in the Python C API, I do not want to spend half a day on finding out which variant to use, and how argument lists differ.
History
Date User Action Args
2020-10-28 14:18:31jwuttkesetrecipients: + jwuttke, jdemeyer
2020-10-28 14:18:31jwuttkesetmessageid: <1603894711.43.0.142721480752.issue42181@roundup.psfhosted.org>
2020-10-28 14:18:31jwuttkelinkissue42181 messages
2020-10-28 14:18:30jwuttkecreate