Re: "The fate of reduce() in Python 3000"

2005-03-13 Thread Luke Palmer
A. Pagaltzis writes: > Hi all, > > so Guido is talking about his reasoning behind dropping lambda, > reduce(), filter() and map() in the next generation of Python: > > http://www.artima.com/weblogs/viewpost.jsp?thread=98196 > > [Prime quote: "I think having the two choices side-by-side just

Re: "The fate of reduce() in Python 3000"

2005-03-13 Thread Uri Guttman
> "AP" == A Pagaltzis <[EMAIL PROTECTED]> writes: AP> [Prime quote: "I think having the two choices side-by-side just AP> requires programmers to think about making a choice that's AP> irrelevant for their program; not having the choice streamlines AP> the thought process."] it just p

Re: "The fate of reduce() in Python 3000"

2005-03-13 Thread Juerd
A. Pagaltzis skribis 2005-03-13 23:40 (+0100): > [Prime quote: "I think having the two choices side-by-side just > requires programmers to think about making a choice that's > irrelevant for their program; not having the choice streamlines > the thought process."] > But, philosophical point of view

"The fate of reduce() in Python 3000"

2005-03-13 Thread A. Pagaltzis
Hi all, so Guido is talking about his reasoning behind dropping lambda, reduce(), filter() and map() in the next generation of Python: http://www.artima.com/weblogs/viewpost.jsp?thread=98196 [Prime quote: "I think having the two choices side-by-side just requires programmers to think about m