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.13:45:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
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 function to speed up all cases mentioned in issue23507: sorted()/list.sort(), min() and max() with the key argument, filter(), map(), some iterators from itertools (groupby(), dropwhile(), takewhile(), accumulate(), filterfalse()), thin wrappers around special method (round(), math.floor(), etc). Use it in wrappers around PyObject_Call() like PyObject_CallFunctionObjArgs(). May be this will cause an effect even on some macrobenchmarks.
Date User Action Args
2016-04-21 13:45:49serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, vstinner, larry, yselivanov
2016-04-21 13:45:49serhiy.storchakasetmessageid: <>
2016-04-21 13:45:49serhiy.storchakalinkissue26814 messages
2016-04-21 13:45:49serhiy.storchakacreate