On Tue, Mar 25, 2008 at 9:42 PM, Olivier Verdier <[EMAIL PROTECTED]> wrote:
> repeats over and over again: lambda is just synctactic sugar for a function
> definition. Here are suggestion for a new name for lambda, which will much
> better describe what it is, namely a *function*.
More specificall
> Olivier Verdier wrote:
> > Any thoughts about that? Any ideas of other better names than "lambda"?
arc uses "fn"
On Tue, Mar 25, 2008 at 7:01 PM, Talin <[EMAIL PROTECTED]> wrote:
> A while back I created and proposed a patch that would change the syntax
> of lambda to be more like a generato
Lennart Regebro wrote:
> On Tue, Mar 25, 2008 at 9:42 PM, Olivier Verdier <[EMAIL PROTECTED]> wrote:
>> repeats over and over again: lambda is just synctactic sugar for a function
>> definition. Here are suggestion for a new name for lambda, which will much
>> better describe what it is, namely a *
On Wed, Mar 26, 2008 at 10:21 AM, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> Some might say that the ugliness of the current syntax is a point in its
> favour ;)
Well, it stops people using it. That's good. :)
> The code will almost always become more readable and self-documenting if
> the fun
There is a dislike of the lambda construction that I just don't understand.
Lambda is very practical in all sorts of situations, like: lambda x,y: x+y.
I just find the name plain silly, that's all. Perhaps you think that all
python programmers or beginners have a LISP background, but that's just no
On Wed, Mar 26, 2008 at 11:32 AM, Olivier Verdier <[EMAIL PROTECTED]> wrote:
> Python has a very clear syntax
Yup. Except the lambda statement of course. :)
(And the clarity of list comprehensions is debateble, but I used them
anyway, because they are dead practical, even though it hurts my
readab
2008/3/26, Neal Norwitz <[EMAIL PROTECTED]>:
> We need to get the tests for Python to be more stable so we can push
> out solid releases. In order to achieve this result, we need tests
> that are *100% reliable* and fail _only when there is a problem with
+1
> Python_. While we aren't near
Folks,
How about we not start a complete rehash of lambda? There was a long thread
several months (or a year?) ago about this. At that time no useful
replacement appeared and Guido decreed the status quo would remain the
status quo. Instead of dreaming up clever lambda replacements, maybe take
Olivier Verdier wrote:
> There is a dislike of the lambda construction that I just don't
> understand. Lambda is very practical in all sorts of situations, like:
> lambda x,y: x+y. I just find the name plain silly, that's all. Perhaps
> you think that all python programmers or beginners have a L
What is this discussion doing in python-3000? Please move it to python-ideas.
--
--Guido van Rossum (home page: http://www.python.org/~guido/)
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubs
On Tue, Mar 25, 2008 at 5:06 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
> On Tue, Mar 25, 2008 at 2:43 PM, Alexander Belopolsky
>
> <[EMAIL PROTECTED]> wrote:
>
> > On Tue, Mar 25, 2008 at 4:26 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
>
> > > It does not even have to be a frozenset. A set works
Neal Norwitz schrieb:
> The next releases of 2.6/3.0 are planned for April 2, just over a week
> from now. There is much work that needs to be done. The buildbots
> are in a pretty sad state and the gods are seeing too much red.
>
> http://www.python.org/dev/buildbot/stable/
> http://www.pyt
>> test_winsound on this buildbot only passes when I have an open remote desktop
>> connection to the (virtual) machine. I have not found any other way to make
>> these
>> tests pass (I tried 'net stop beep', disabling the sound driver, removing the
>> sound driver, disconnecting the hosts sound
Georg Brandl schrieb:
> Perhaps make it an optional resource?
In the py3k branch I've assigned the audio resource to the winsound
tests. Only regrtest.py -uall or -uaudio runs the winsound test. Reason:
the test sound was freaking out my poor cat. :/
Christian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2008, at 2:21 AM, Neal Norwitz wrote:
> The next releases of 2.6/3.0 are planned for April 2, just over a week
> from now. There is much work that needs to be done. The buildbots
> are in a pretty sad state and the gods are seeing too much
Thomas Heller schrieb:
> Neal Norwitz schrieb:
>> The next releases of 2.6/3.0 are planned for April 2, just over a week
>> from now. There is much work that needs to be done. The buildbots
>> are in a pretty sad state and the gods are seeing too much red.
>>
>> http://www.python.org/dev/build
On 26/03/2008, Thomas Heller <[EMAIL PROTECTED]> wrote:
> What I would like to see is a way to disable certain tests on certain
> machines;
> maybe by setting environment variables?
Could this be done by something like the following (completely
untested no time at the moment) change to regrte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2008, at 8:14 AM, Facundo Batista wrote:
> 2008/3/26, Neal Norwitz <[EMAIL PROTECTED]>:
>
>> We need to get the tests for Python to be more stable so we can push
>> out solid releases. In order to achieve this result, we need tests
>> that
On Wed, Mar 26, 2008 at 9:18 AM, Alexander Belopolsky
<[EMAIL PROTECTED]> wrote:
>
> On Tue, Mar 25, 2008 at 5:06 PM, Adam Olsen <[EMAIL PROTECTED]> wrote:
> > On Tue, Mar 25, 2008 at 2:43 PM, Alexander Belopolsky
> >
> > <[EMAIL PROTECTED]> wrote:
> >
> > > On Tue, Mar 25, 2008 at 4:26 PM, Ad
On Wed, Mar 26, 2008 at 9:04 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Mar 26, 2008, at 8:14 AM, Facundo Batista wrote:
> > 2008/3/26, Neal Norwitz <[EMAIL PROTECTED]>:
> >
> >> We need to get the tests for Python to be more stable s
Christian Heimes schrieb:
> Georg Brandl schrieb:
>> Perhaps make it an optional resource?
>
> In the py3k branch I've assigned the audio resource to the winsound
> tests. Only regrtest.py -uall or -uaudio runs the winsound test. Reason:
> the test sound was freaking out my poor cat. :/
I feel wi
On Wed, Mar 26, 2008 at 1:21 AM, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> The next releases of 2.6/3.0 are planned for April 2, just over a week
> from now. There is much work that needs to be done. The buildbots
> are in a pretty sad state and the gods are seeing too much red.
>
> http://www.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 26, 2008, at 5:10 PM, Benjamin Peterson wrote:
> There are also some backporting issues in that pile. Should those
> hold up
> betas? (when we get there)
Yes, but I would simply release the monthly alpha and push the beta
back a month.
-
If this were ever to change, my preference would be to
find a syntax that doesn't use a keyword at all.
Lambdas are most useful when the body is extremely
short. But in those cases, the word 'lambda' itself
is nearly as long as the body, which destroys about
half the benefit of using it in the fir
Alexander Belopolsky wrote:
> 1. Do nothing: dicts are built incrementally, and sets in batch.
> 2. Implement batch processing for dict literals.
> 3. Implement incremental processing for sets.
My thought is that sets are the odd one out here.
Tuples are created batchwise because, being immutabl
We had a short discussion about Python 3.0 porting during our bi-weekly
Python meeting at Google, and it was suggested that I write up what was
discussed.
From reading the Python 3000 mailing list over the last several months,
it is apparent that there are many different approaches to making t
> For new code, however, there is an alternative strategy that doesn't
> involve 2to3 at all, which is to write code in the "greatest common
> subset" of 2.6 and 3.0.
>
> As Lennart Regbro pointed out earlier, this common subset is actually
> quite large (larger than Guido originally intended,
Martin v. Löwis wrote:
>> For new code, however, there is an alternative strategy that doesn't
>> involve 2to3 at all, which is to write code in the "greatest common
>> subset" of 2.6 and 3.0.
>>
>> As Lennart Regbro pointed out earlier, this common subset is actually
>> quite large (larger than
28 matches
Mail list logo
