Message285411
tp_fastcall.patch modifies property_descr_get() to use tp_fastcall if available, or use the cached tuple. Once performances are validated (no regression), the cached tuple as to pass position arguments, should go away.
By the way, msg285390 uses the following micro-benchmark:
---
import perf
bench = perf.Runner()
bench.timeit("namedtuple.attr",
"a.a",
"from collections import namedtuple as n; a = n('n', 'a b c')(1, 2, 3)",
duplicate=20)
---
It tests property_descr_get() with operator.itemgetter(). It would be nice to benchmark property_descr_get() with other functions. |
|
Date |
User |
Action |
Args |
2017-01-13 15:51:14 | vstinner | set | recipients:
+ vstinner, methane, serhiy.storchaka |
2017-01-13 15:51:14 | vstinner | set | messageid: <1484322674.89.0.692607587334.issue29259@psf.upfronthosting.co.za> |
2017-01-13 15:51:14 | vstinner | link | issue29259 messages |
2017-01-13 15:51:14 | vstinner | create | |
|