From: Guido van Rossum <guido@python.org>
Date: Tue, 23 Jul 2002 03:44:35 +0000 (+0000)
Subject: News about StopIteration as a "sink state".
X-Git-Tag: v2.3c1~4890
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2d5389c08f4e9b4f325fba6dc88be1db9d0ba3e0;p=thirdparty%2FPython%2Fcpython.git

News about StopIteration as a "sink state".
---

diff --git a/Misc/NEWS b/Misc/NEWS
index 0a1ce88e11ba..f8f3b7f5d222 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -6,6 +6,14 @@ Type/class unification and new-style classes
 
 Core and builtins
 
+- All standard iterators now ensure that, once StopIteration has been
+  raised, all future calls to next() on the same iterator will also
+  raise StopIteration.  There used to be various counterexamples to
+  this behavior, which could caused confusion or subtle program
+  breakage, without any benefits.  (Note that this is still an
+  iterator's responsibility; the iterator framework does not enforce
+  this.)
+
 - Ctrl+C handling on Windows has been made more consistent with
   other platforms.  KeyboardInterrupt can now reliably be caught,
   and Ctrl+C at an interative prompt no longer terminates the