STINNER Victor <vstin...@python.org> added the comment:
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.stin...@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.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue45439>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
