[issue26814] Add a new _PyObject_CallStack() function which avoids the creation of a tuple or dict for arguments

Larry Hastings added the comment: Yes, I've been working on a patch to do this as well. I called the calling convention METH_RAW, to go alongside METH_ZERO METH_O etc. My calling convention was exactly the same as yours: PyObject *(PyObject *o, PyObject **stack, int na, int nk). I only had

[issue26814] Add a new _PyObject_CallStack() function which avoids the creation of a tuple or dict for arguments

Serhiy Storchaka added the comment: With call_stack-2.patch attribute access in namedtuple is only 25% slower than attribute access in ordinary Python object! Definitely this this worth to continue to experiment! But adding new slot to PyTypeObject sets the bar too high. Try to use your

[issue26814] Add a new _PyObject_CallStack() function which avoids the creation of a tuple or dict for arguments

STINNER Victor added the comment: call_stack-2.patch: A little bit more complete patch, it adds a tp_call_stack field to PyTypeObject an use it in _PyObject_CallStack(). Updated microbenchmark on Python 3.6, best of 3 runs: ./python -m timeit -r 11 -s "from collections import namedtuple as n;

[issue26814] Add a new _PyObject_CallStack() function which avoids the creation of a tuple or dict for arguments

Serhiy Storchaka added the comment: See also issue23507. May be your function help to optimize filter(), map(), sorted()? -- ___ Python tracker ___

[issue26814] Add a new _PyObject_CallStack() function which avoids the creation of a tuple or dict for arguments

STINNER Victor added the comment: Microbenchmark on Python 3.6, best of 3 runs: ./python -m timeit -r 11 -s "from collections import namedtuple as n; a = n('n', 'a b c')(1, 2, 3)" -- "a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a; a.a" * Python 3.6

[issue26814] Add a new _PyObject_CallStack() function which avoids the creation of a tuple or dict for arguments

Serhiy Storchaka added the comment: "Stack" in the function name looks a little confusing. I understand that this is related to the stack of bytecode interpreter, but this looks as raising pretty deep implementation detail. The way of packing positional and keyword arguments in the continuous

[issue26814] Add a new _PyObject_CallStack() function which avoids the creation of a tuple or dict for arguments

Changes by STINNER Victor : -- nosy: +yselivanov ___ Python tracker ___ ___

[issue26814] Add a new _PyObject_CallStack() function which avoids the creation of a tuple or dict for arguments

New submission from STINNER Victor: Attached patch adds the following new function: PyObject* _PyObject_CallStack(PyObject *func, PyObject **stack, int na, int nk); where na is the number of positional arguments and nk is