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 vstinner
Recipients methane, serhiy.storchaka, vstinner
Date 2017-01-13.15:51:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484322674.89.0.692607587334.issue29259@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2017-01-13 15:51:14vstinnersetrecipients: + vstinner, methane, serhiy.storchaka
2017-01-13 15:51:14vstinnersetmessageid: <1484322674.89.0.692607587334.issue29259@psf.upfronthosting.co.za>
2017-01-13 15:51:14vstinnerlinkissue29259 messages
2017-01-13 15:51:14vstinnercreate