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, vstinner
Date 2017-01-19.11:33:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484825581.48.0.790581995103.issue29318@psf.upfronthosting.co.za>
In-reply-to
Content
Example:
---
def func(x, y):
    print(x, y)

def proxy2(func, **kw):
    func(**kw)

def proxy1(func, **kw):
    proxy2(func, **kw)
---

The "proxy2(func, **kw)" call in proxy1() is currently inefficient: _PyFunction_FastCallDict() converts the dictionary into a C array [key1, value1, key2, value2, ...] and then _PyEval_EvalCodeWithName() rebuilds the dictionary from the C array.

Since "func(*args, **kw)" proxies are common in Python, especially to call the parent constructor when overriding __init__, I think that it would be interesting to optimize this code path.

I first expected that it was a regression of FASTCALL, but Python < 3.6 doesn't optimize this code neither.
History
Date User Action Args
2017-01-19 11:33:01vstinnersetrecipients: + vstinner, methane
2017-01-19 11:33:01vstinnersetmessageid: <1484825581.48.0.790581995103.issue29318@psf.upfronthosting.co.za>
2017-01-19 11:33:01vstinnerlinkissue29318 messages
2017-01-19 11:33:00vstinnercreate