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 serhiy.storchaka
Recipients larry, rhettinger, serhiy.storchaka, vstinner, yselivanov
Date 2016-04-21.09:53:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
"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 array is not clear. Wouldn't be better to provide separate arguments for positional and keyword arguments?

What is the performance effect of using this function? For example compare the performance of namedtuple's attribute access of current code, the code with with this patch, and unoptimized code in 3.4:

    ./python -m timeit -r 11 -s "from collections import namedtuple as n; a = n('n', 'a b c')(1, 2, 3)" -- "a.a"

Is there any use of this function with keyword arguments?
Date User Action Args
2016-04-21 09:53:53serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, vstinner, larry, yselivanov
2016-04-21 09:53:53serhiy.storchakasetmessageid: <>
2016-04-21 09:53:53serhiy.storchakalinkissue26814 messages
2016-04-21 09:53:53serhiy.storchakacreate