➜
See More

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 lemburg
Recipients BreamoreBoy, docs@python, lemburg, ncoghlan, pitrou, robquad
Date 2017-02-14.10:03:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <[email protected]>
In-reply-to
Content 
The PyEval_Call*() APIs indeed predate the PyObject_Call*() ones. The PyObject_Call*() APIs came into existence when the abstract layer was added in Python 1.3.

The PyObject_Call*() APIs lacked a way to call an object with keyword arguments for a long time. I guess that's what most people continued to use the PyEval_Call*() ones. The latter also provide better protection against wrong parameters. The interpreter itself used them interchangeably.
History
Date User Action Args
2017-02-14 10:03:38lemburgsetrecipients: + lemburg, ncoghlan, pitrou, docs@python, BreamoreBoy, robquad
2017-02-14 10:03:38lemburgsetmessageid: <[email protected]>
2017-02-14 10:03:38lemburglinkissue11165 messages
2017-02-14 10:03:38lemburgcreate