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 jdemeyer
Recipients Mark.Shannon, jdemeyer, methane, petr.viktorin, vstinner
Date 2019-06-19.09:35:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1560936931.61.0.893195452608.issue37337@roundup.psfhosted.org>
In-reply-to
Content
To augment the various PyObject_CallMethod...() functions, we add _PyObject_VectorcallMethod() which uses the vectorcall calling convention. To be consistent with the other vectorcall functions, this function is provisional for now.

For efficiency, the "self" argument is NOT passed as separate argument but as part of the usual args array. In other words, the call looks like an unbound method call.

I am also adding _PyObject_VectorcallMethodId() taking a _Py_Identifier* as argument and convenience functions PyObject_CallMethodNoArgs() and _PyObject_CallMethodIdNoArgs(), analogous to the recently added PyObject_CallNoArgs().
History
Date User Action Args
2019-06-19 09:35:31jdemeyersetrecipients: + jdemeyer, vstinner, petr.viktorin, methane, Mark.Shannon
2019-06-19 09:35:31jdemeyersetmessageid: <1560936931.61.0.893195452608.issue37337@roundup.psfhosted.org>
2019-06-19 09:35:31jdemeyerlinkissue37337 messages
2019-06-19 09:35:31jdemeyercreate