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 pitrou
Recipients brett.cannon, larry, pitrou, r.david.murray, yselivanov
Date 2015-05-14.15:53:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Le 14/05/2015 17:45, Yury Selivanov a écrit :
> Well, the docs example only binds explicit defaults in function
> signature. Implicit defaults for *args and **kwargs (`()` and `{}`)
> aren't usually useful (in my opinion).

When the defaults are filled I expect ba.arguments to be "complete",
that is have a value for every signature parameter. Otherwise I have to
special-case *args and **kwargs.

> Do you guys have any good use case for such method?

A use case was given in issue22998.
My use case is JIT-compiling functions and function calls in Numba. We
reimplement the function calls ourselves, so need a complete mapping of
arguments to values.
Date User Action Args
2015-05-14 15:53:41pitrousetrecipients: + pitrou, brett.cannon, larry, r.david.murray, yselivanov
2015-05-14 15:53:41pitroulinkissue24190 messages
2015-05-14 15:53:40pitroucreate