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 vstinner
Recipients vstinner
Date 2017-01-10.23:05:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484089500.65.0.838677833824.issue29233@psf.upfronthosting.co.za>
In-reply-to
Content
Recently, I modified call_method() and call_maybe() of Objects/typeobject.c to avoid the creation of a temporary tuple: replace Py_VaBuildValue()+PyObject_Call() with the new _PyObject_VaCallFunctionObjArgs().

But while working on the issue #28870, I noticed that _PyObject_VaCallFunctionObjArgs() is not efficient and can be avoided. In typeobject.c, the number of arguments is hardcoded, so we don't need complex functions to compute the number of arguments and decide to allocate an array on the stack or on the heap.
History
Date User Action Args
2017-01-10 23:05:00vstinnersetrecipients: + vstinner
2017-01-10 23:05:00vstinnersetmessageid: <1484089500.65.0.838677833824.issue29233@psf.upfronthosting.co.za>
2017-01-10 23:05:00vstinnerlinkissue29233 messages
2017-01-10 23:05:00vstinnercreate