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 rmccampbell7
Recipients rmccampbell7
Date 2014-06-07.05:10:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1402117848.15.0.331618951416.issue21684@psf.upfronthosting.co.za>
In-reply-to
Content
I'm not sure if this is really a bug, but it is unexpected behavior. When you call "bind" on a Python 3.3 signature object, if you omit an optional argument, the default is not provided in the arguments dict. Similarly, if there is a "var positional" or "var keyword" parameter but there are no extra arguments, it will not be included. To emulate the effect on the namespace of an actual function, I would expect these to be included, as an empty tuple/dict in the case of variable arguments. I realize the current behavior may be useful in some cases, but if so, then another method could be added: bind_full, which would include all parameters of the signature.
History
Date User Action Args
2014-06-07 05:10:48rmccampbell7setrecipients: + rmccampbell7
2014-06-07 05:10:48rmccampbell7setmessageid: <1402117848.15.0.331618951416.issue21684@psf.upfronthosting.co.za>
2014-06-07 05:10:48rmccampbell7linkissue21684 messages
2014-06-07 05:10:47rmccampbell7create