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 yselivanov
Recipients brett.cannon, larry, pitrou, r.david.murray, yselivanov
Date 2015-05-14.15:45:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1431618340.7.0.127097117514.issue24190@psf.upfronthosting.co.za>
In-reply-to
Content
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).

Do you guys have any good use case for such method?  I use the Signature API extensively for argument types validation and for serialization of RPC calls, but I never needed this functionality from BoundArguments.
History
Date User Action Args
2015-05-14 15:45:40yselivanovsetrecipients: + yselivanov, brett.cannon, pitrou, larry, r.david.murray
2015-05-14 15:45:40yselivanovsetmessageid: <1431618340.7.0.127097117514.issue24190@psf.upfronthosting.co.za>
2015-05-14 15:45:40yselivanovlinkissue24190 messages
2015-05-14 15:45:40yselivanovcreate