The docs http://docs.python.org/2/library/functions.html#all provide some equivalent code for all builtin (and similarly for any):

def all(iterable):
    for element in iterable:
        if not element:
            return False
    return True

The behaviour is clearly documented as short-circuiting, but the cases contained in test_builtin.py are lacking any test coverage for the short-circuiting behaviour.  You could implement any/all in a broken way that still passes the current tests (consuming more of a generator than you want to for example), so it is important to guarantee the short-circuiting.

My patch adds two simple test cases to make this behaviour explicit.

New changeset 124237eb5de9 by Ezio Melotti in branch '2.7':
#17255: test short-circuiting behavior of any()/all().  Patch by Wim Glenn.
http://hg.python.org/cpython/rev/124237eb5de9

New changeset 34b7240d678b by Ezio Melotti in branch '3.2':
#17255: test short-circuiting behavior of any()/all().  Patch by Wim Glenn.
http://hg.python.org/cpython/rev/34b7240d678b

New changeset 576d2c885eb6 by Ezio Melotti in branch '3.3':
#17255: merge with 3.2.
http://hg.python.org/cpython/rev/576d2c885eb6

New changeset c65fcedc511c by Ezio Melotti in branch 'default':
#17255: merge with 3.3.
http://hg.python.org/cpython/rev/c65fcedc511c

Fixed, thanks for the report and the patch!