Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Default arguments in Python - the return - running out of ideas but...
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
George Sakkis  
View profile  
 More options May 13 2009, 8:10 pm
From: George Sakkis <george.sak...@gmail.com>
Date: Wed, 13 May 2009 20:10:42 -0400
Local: Wed, May 13 2009 8:10 pm
Subject: Re: [Python-ideas] Default arguments in Python - the return - running out of ideas but...

On Wed, May 13, 2009 at 7:08 PM, Terry Reedy <tjre...@udel.edu> wrote:
> Bruce Leban wrote:

>> Here's what I'd like:

>> def myfunc(a, b, c = *lambda: expression):
>>  stuff

>> The use of the lambda keyword here makes the scope of any variables in the
>> expression clear. The use of the prefix * makes the syntax invalid today,
>> suggests dereferencing and doesn't hide the overhead. This is equivalent to:

> There is a proposal, which I thought was accepted in principle, to make '*
> seq' valid generally, not just in arg-lists. to mean 'unpack the sequence'.
> * (lambda:1,2)() would then be valid, and without the call, would be a
> runtime, not syntax error.

> Other than that ;0(, it would be an interesting idea.

Then how about putting the * before the parameter ?

    def myfunc(a, b, *c = lambda: expression):

It's currently a syntax error, although the fact that "*arg" and
"*arg=default" would mean something completely different is
problematic. Still the same idea can be applied for some other
operator (either valid already or not).

Regardless of the actual operator, I came up with the following
additional subproposals.

Subproposal (1): Get rid of the explicit lambda for dynamic arguments. That is,

    def myfunc(a, b, *x=[]):

would be equivalent to what previous proposals would write as

    def myfunc(a, b, *x=lambda: []):

Subproposal (2): If subproposal (1) is accepted, we could get for free
(in terms of syntax at least) dynamic args depending on previous ones.
That is,

    def myfunc(a, b, *m=(a+b)/2):

would mean

    def myfunc(a, b, *m = lambda a,b: (a+b)/2):

with the lambda being passed the values of a and b at runtime.

Thoughts ?

George
_______________________________________________
Python-ideas mailing list
Python-id...@python.org
http://mail.python.org/mailman/listinfo/python-ideas


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.