[issue33829] C API: provide new object protocol helper

Change by Serhiy Storchaka : -- resolution: -> rejected stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue33829] C API: provide new object protocol helper

Jeroen Demeyer added the comment: I agree with rejecting and closing this issue. -- nosy: +jdemeyer ___ Python tracker ___ ___

[issue33829] C API: provide new object protocol helper

Cheryl Sabella added the comment: It seems that this issue is languishing without any additional comments from the OP. Should it be closed as rejected? Thanks! -- nosy: +cheryl.sabella ___ Python tracker

[issue33829] C API: provide new object protocol helper

Change by Pablo Galindo Salgado : -- nosy: +pablogsal ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33829] C API: provide new object protocol helper

STINNER Victor added the comment: > PyObject_CallMethodArgs(PyObject *obj, const char *name, PyObject *args, > PyObject *kwargs) This API is not efficient. It requires to create a temporary tuple and dictionary to pass position and keyword arguments. Look at FASTCALL which has a very

[issue33829] C API: provide new object protocol helper

Serhiy Storchaka added the comment: Is this case common enough for adding special API? The name PyObject_CallMethodArgs looks too similar to the existing name PyObject_CallMethodObjArgs, this will make confusion. If add an API that accepts the method name as C string, you need to add also

[issue33829] C API: provide new object protocol helper

Change by Roundup Robot : -- keywords: +patch pull_requests: +7244 stage: -> patch review ___ Python tracker ___ ___

[issue33829] C API: provide new object protocol helper

New submission from Bartosz Gołaszewski : If we want to call an object's method from C code and pass it the args and kwargs tuples unchanged, we need to first retrieve the callable object using PyObject_GetAttrString(), then call it using PyObject_Call(). I would like to propose wrapping the