Bill Janssen wrote: > Though, from the standpoint of pragmatism, removing "reduce" from the > built-in space will break code (*my* code, among others), and leaving > it in will not affect "purity", as both "map" and "reduce" are being > left in. So leaving it alone seems the more Pythonic response to me.
Python 3000 tries to reduce (hehe) the amount of builtins so reduce was removed since it is rarely used. I don't understand why map and filter wasn't moved to functools, too. You made one good point. At the moment you can't write code that utilizes reduce and works under 2.6 and 3.0. from functools import reduce fails in 2.6. The 2to3 suite has no fixer for reduce. My patch removes the flaw: http://www.python.org/sf/1739906 Christian _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
