On Tue, Oct 13, 2015 at 10:26 AM, Random832 <random...@fastmail.com> wrote: > "R. David Murray" <rdmur...@bitdance.com> writes: > >> On Tue, 13 Oct 2015 14:59:56 +0300, Stefan Mihaila >> <stefanmihail...@gmail.com> wrote: >>> Maybe it's just python2 habits, but I assume I'm not the only one >>> carelessly thinking that "iterating over an input a second time will >>> result in the same thing as the first time (or raise an error)". >> >> This is the way iterators have always worked. > > It does raise the question though of what working code it would actually > break to have "exhausted" iterators raise an error if you try to iterate > them again rather than silently yield no items.
You mean like this? >>> m = map(int, '1234') >>> list(m) [1, 2, 3, 4] >>> next(m) Traceback (most recent call last): File "<stdin>", line 1, in <module> StopIteration It just happens that 'list()' and 'for ...' handle StopIteration for you. -- Zach _______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
