Chris Smith wrote: > My question is, why not move them into, say, a "functional" library, > so that legacy code can be handled via an import, and those heads > preferring to think that way can be satisfied, and those little corner > cases not handled by the newer, sweller syntaxes can still be managed? > IOW, just ripping them out of the core and leaving everyone in the > lurch doesn't seem too pythonic to me.
Python 3000 will be breaking more backwards compatibility than map/reduce/filter. That legacy code won't work anyways. I predict, though, that one of the first 3rd party modules to come out for Python 3000 will be such a library. -- Robert Kern [EMAIL PROTECTED] "In the fields of hell where the grass grows high Are the graves of dreams allowed to die." -- Richard Harter -- http://mail.python.org/mailman/listinfo/python-list
