From e0a674f8d445007cd175d2970c197364cee34ef5 Mon Sep 17 00:00:00 2001
From: Fred Drake <fdrake@acm.org>
Date: Mon, 6 May 2002 16:05:01 +0000
Subject: [PATCH] Add a note explaining the interaction between unbuffered
 input and xreadlines.xreadlines(). This closes SF patch #552804.

---
 Doc/lib/libxreadlines.tex | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/Doc/lib/libxreadlines.tex b/Doc/lib/libxreadlines.tex
index d824fc3e8c63..1b8a341c2c7c 100644
--- a/Doc/lib/libxreadlines.tex
+++ b/Doc/lib/libxreadlines.tex
@@ -38,7 +38,10 @@ former case.
 \begin{funcdesc}{xreadlines}{fileobj}
   Return a new xreadlines object which will iterate over the contents
   of \var{fileobj}.  \var{fileobj} must have a \method{readlines()}
-  method that supports the \var{sizehint} parameter.
+  method that supports the \var{sizehint} parameter.  \strong{Note:}
+  Because the \method{readlines()} method buffers data, this
+  effectively ignores the effects of setting the file object as
+  unbuffered.
 \end{funcdesc}
 
 An xreadlines object \var{s} supports the following sequence
-- 
2.47.3