diff options
| author | Guido van Rossum <guido@python.org> | 2002-07-23 03:44:35 (GMT) |
|---|---|---|
| committer | Guido van Rossum <guido@python.org> | 2002-07-23 03:44:35 (GMT) |
| commit | 2d5389c08f4e9b4f325fba6dc88be1db9d0ba3e0 (patch) | |
| tree | b759a46a59b3e5075a34aaeada66b8d405438d65 /Misc | |
| parent | 79f0a106e69db8d0e913fa266c9ff6e3366c2828 (diff) | |
| download | cpython-2d5389c08f4e9b4f325fba6dc88be1db9d0ba3e0.zip cpython-2d5389c08f4e9b4f325fba6dc88be1db9d0ba3e0.tar.gz cpython-2d5389c08f4e9b4f325fba6dc88be1db9d0ba3e0.tar.bz2 | |
News about StopIteration as a "sink state".
Diffstat (limited to 'Misc')
| -rw-r--r-- | Misc/NEWS | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -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 |