> My guess is that, after sum, the functions used in reduce get a lot more > diverse, and that trying to replace all of them with builtins is not > feasible. That matches my intuition. I figure even if we just started deprecating reduce() without offering a replacement there wouldn't be many complaints. reduce() just doesn't get enough mileage. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4