Antoine Pitrou added the comment:
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.
----------
_______________________________________
Python tracker <[email protected]>
<http://bugs.python.org/issue24190>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
