➜

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 2021-10-13.00:31:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1634085116.27.0.77129229613.issue45439@roundup.psfhosted.org>
In-reply-to
Content 
5 years ago, I added _PyObject_CallArg1() (similar to PyObject_CallOneArg()) and then I removed it since it consumed more stack memory than existing function, whereas I added _PyObject_CallArg1() to reduce the stack consumption.

commit 7bfb42d5b7721ca26e33050d025fec5c43c00058
Author: Victor Stinner <victor.stinner@gmail.com>
Date:   Mon Dec 5 17:04:32 2016 +0100

    Issue #28858: Remove _PyObject_CallArg1() macro
    
    Replace
       _PyObject_CallArg1(func, arg)
    with
       PyObject_CallFunctionObjArgs(func, arg, NULL)
    
    Using the _PyObject_CallArg1() macro increases the usage of the C stack, which
    was unexpected and unwanted. PyObject_CallFunctionObjArgs() doesn't have this
    issue.
History
Date User Action Args
2021-10-13 00:31:56vstinnersetrecipients: + vstinner
2021-10-13 00:31:56vstinnersetmessageid: <1634085116.27.0.77129229613.issue45439@roundup.psfhosted.org>
2021-10-13 00:31:56vstinnerlinkissue45439 messages
2021-10-13 00:31:56vstinnercreate