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 ncoghlan
Recipients ncoghlan
Date 2019-05-22.12:19:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1558527581.74.0.915249229552.issue37010@roundup.psfhosted.org>
In-reply-to
Content
(Splitting out a separate performance issue from https://bugs.python.org/issue36751#msg342683)

There can be two quite different reasons for inspecting a function signature:

* inspecting arbitrary functions to learn as much about them as possible in order to present good coding hints and other guidance to a developer
* inspecting function and method implementations passed to a runtime API in order to call them correctly

inspect.signature focuses on the former use case, and as a result ended up being markedly slower than the simpler inspect.getfullargspec implementation that it replaced.

At the moment, inspect.getfullargspec is being kept around solely as a backwards compatibility API - it calls inspect.signature internally, but then throws away the rich objects that function creates, replacing them with simple Python builtins.

It seems plausible that we could reverse that relationship, and instead have inspect.signature use inspect.getfullargspec as a lower level API that produces less self-descriptive output, but also avoids creating a lot of instances of custom Python objects.

(Sample performance data can be seen in https://gist.github.com/zzzeek/0eb0636fa3917f36ffd887d9f765c208)
History
Date User Action Args
2019-05-22 12:19:41ncoghlansetrecipients: + ncoghlan
2019-05-22 12:19:41ncoghlansetmessageid: <1558527581.74.0.915249229552.issue37010@roundup.psfhosted.org>
2019-05-22 12:19:41ncoghlanlinkissue37010 messages
2019-05-22 12:19:41ncoghlancreate