There is much confusion over this, and I still, to this day, cannot figure out why.
Attention all those who think that Python is abandoning functional programming!!
Python 3000 will not "reject" lambda, map, filter, and reduce. It NEVER was. Instead, the language was going to be *refactored*.
Enough of an uproar occured where lambda will stay in as-is.
However, map, filter, and reduce will either be replaced outright with list comprehensions (thank you Haskell -- what was that about dropping its functional roots again?) or will be moved off into another module which you have to import to use them. If my memory of the e-mail with Guido Van Rossum some time ago is correct, this module will be written as a C module, so there will be no performance hit.
Remember, Python 3000 is a refactoring, to clean up the language from its current mess. Feature for feature, it not only matches the current Python, but even *exceeds* it.
Python 3000
There is much confusion over this, and I still, to this day, cannot figure out why.
Attention all those who think that Python is abandoning functional programming!!
Python 3000 will not "reject" lambda, map, filter, and reduce. It NEVER was. Instead, the language was going to be *refactored*.
Enough of an uproar occured where lambda will stay in as-is.
However, map, filter, and reduce will either be replaced outright with list comprehensions (thank you Haskell -- what was that about dropping its functional roots again?) or will be moved off into another module which you have to import to use them. If my memory of the e-mail with Guido Van Rossum some time ago is correct, this module will be written as a C module, so there will be no performance hit.
Remember, Python 3000 is a refactoring, to clean up the language from its current mess. Feature for feature, it not only matches the current Python, but even *exceeds* it.