RetroSearch Browse

Thu Aug 24 02:30:55 CEST 2006 · https://mail.python.org/pipermail/python-dev/2006-August/068449.html

On 8/23/06, Georg Brandl <g.brandl at gmx.net> wrote:
>
> Brett Cannon wrote:
> > I have been spending my Google sprint time on writing and implementing
> > PEP 362 (http://www.python.org/dev/peps/pep-0362/), which finally
> > defines Signature objects for functions.  With the implementation at a
> > place I am happy with, I wanted to ask about the open issues with the
> PEP.
>
> While reading the PEP, I stumbled over the description of the bind()
> method.
>
> As I understand the implementation patch, the parameter names will be keys
> and
> the arguments values in the resulting dictionary, but this sentence looks
> to
> me as if it describes it the opposite way (it also doesn't clarify that
> "parameter" means "parameter name"):
>
> * bind(*args, **kwargs) -> dict
>      Create a mapping from argument to parameter for the signature (see
>      `Open Issues`_ for question of how to handle tuples).

You're right, it's a typo.

Another question: could it be helpful to make Parameter.default_value a
> weak reference?

Perhaps, but I don't think it is necessarily required.  I can change it if
others want to go that way, but for now I am happy with the way it is.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/python-dev/attachments/20060823/d557359c/attachment.html 

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2006-August/068449.html below:

[Python-Dev] PEP 362 open issues