From: Guido van Rossum <guido@python.org>
Date: Tue, 6 Aug 2002 16:20:26 +0000 (+0000)
Subject: Files are now their own iterator.  The xreadlines method and module
X-Git-Tag: v2.3c1~4673
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b57089cdf8b63b38ca736785c9fcc38a9fce89da;p=python

Files are now their own iterator.  The xreadlines method and module
are obsolete.
---

diff --git a/Misc/NEWS b/Misc/NEWS
index 19b3651869..3c5c834820 100644
--- a/Misc/NEWS
+++ b/Misc/NEWS
@@ -6,6 +6,16 @@ Type/class unification and new-style classes
 
 Core and builtins
 
+- File objects are now their own iterators.  For a file f, iter(f) now
+  returns f (unless f is closed), and f.next() is similar to
+  f.readline() when EOF is not reached; however, f.next() uses a
+  readahead buffer that messes up the file position, so mixing
+  f.next() and f.readline() (or other methods) doesn't work right.
+  Calling f.seek() drops the readahead buffer, but other operations
+  don't.  It so happens that this gives a nice additional speed boost
+  to "for line in file:"; the xreadlines method and corresponding
+  module are now obsolete.
+
 - Encoding declarations (PEP 263, phase 1) have been implemented.  A
   comment of the form "# -*- coding: <encodingname> -*-" in the first
   or second line of a Python source file indicates the encoding.
@@ -167,6 +177,8 @@ Core and builtins
 
 Extension modules
 
+- The xreadlines module is slated for obsolescence.
+
 - The strptime function in the time module is now always available (a
   Python implementation is used when the C library doesn't define it).