Here are some additions to documentation of a few functions:

all, any: alternative definitions using functools.reduce
enumerate: alternative definition using zip and itertools.count
sum: equivalent definition using functools.reduce and operator.add
functools.reduce: equivalent definitions, use operator.add in example
itertools.accumulate: point to functools.reduce
itertools.filterfalse: point to filter

Most of these changes should not be applied: the "alternate" equivalents in terms of reduce() will not help understanding,  Equivalents for reduce() may be useful, but I would limit them to one per case, possibly even just one function that covers both cases.

I'm deferring to Raymond for the changes to the itertools docs.

How would you give a single definition of reduce() that helps people to understand both 2-arg and 3-arg variants? The way it is implemented in C is impossible to duplicate in pure Python; the best you could do is a hack that works unless someone *tries* to break it, but that would just be confusing.

What about

def reduce(function, iterable, initializer=None):
    it = iter(iterable)
    if initializer is None:
        value = next(it)
    else:
        value = initializer
    for element in it:
        value = function(value, element)
    return value

Remember, an equivalent doesn't have to be 100% compatible, it is a way for the user to quickly get an idea what the function does.

I think the reduce equivalent given by Georg would be excellent.

I think the enumerate equivalent already given is fine because I think equivalents should use basic syntax (for loops), not something that might be more obscure.

Almost all of these make the docs worse and should not be applied.  The purpose of the "equivalent" code is simply to make the documentation clearer, not to show all the ways it could have been done.

I do think Georg's reduce() equivalent should be added because it is clearer than the current prose description.

What do you think of the two references added to the itertools docs?

The reference from accumulate() to reduce() may be useful.

I'm opposed to most of the other equivalents and cross-references.  They bloat the docs without adding value.  Terry is right in saying that the equivalent for enumerate() is better as a basic loop than as a composition of functional tools.   I think the OP has missed what the purpose of the code equivalents was trying to do.

I agree. Will prepare a patch to the reduce() doc.

New changeset 3b6401c27e39 by Raymond Hettinger in branch '3.3':
Issue #19202:  Add cross-reference and a rough code equivalent
http://hg.python.org/cpython/rev/3b6401c27e39

Thanks Georg.