From 4ffe9a064022b973ab152d108b13c470af486a74 Mon Sep 17 00:00:00 2001 From: Sandro Tosi Date: Wed, 15 Aug 2012 21:37:19 +0200 Subject: [PATCH] clarify in/not in in case of infinite iterators; thanks to Sergey Skovorodkin from docs@ --- Doc/howto/functional.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/howto/functional.rst b/Doc/howto/functional.rst index 9636c6cd576..836ec6da413 100644 --- a/Doc/howto/functional.rst +++ b/Doc/howto/functional.rst @@ -244,9 +244,9 @@ Built-in functions such as :func:`max` and :func:`min` can take a single iterator argument and will return the largest or smallest element. The ``"in"`` and ``"not in"`` operators also support iterators: ``X in iterator`` is true if X is found in the stream returned by the iterator. You'll run into obvious -problems if the iterator is infinite; ``max()``, ``min()``, and ``"not in"`` +problems if the iterator is infinite; ``max()``, ``min()`` will never return, and if the element X never appears in the stream, the -``"in"`` operator won't return either. +``"in"`` and ``"not in"`` operators won't return either. Note that you can only go forward in an iterator; there's no way to get the previous element, reset the iterator, or make a copy of it. Iterator objects