From: Fred Drake <fdrake@acm.org>
Date: Thu, 25 Mar 2004 16:51:12 +0000 (+0000)
Subject: Note that reading from a socket may not always return all of the
X-Git-Tag: v2.4a1~567
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=504ca68e20e01a42d89431a4562b3a72c9d62961;p=python

Note that reading from a socket may not always return all of the
remaining content of a stream when expected to do so.
Closes SF bug #725265.  Should be backported to Python 2.3.x.
---

diff --git a/Doc/lib/liburllib.tex b/Doc/lib/liburllib.tex
index a2ebc327e4..47348c1bc6 100644
--- a/Doc/lib/liburllib.tex
+++ b/Doc/lib/liburllib.tex
@@ -29,6 +29,10 @@ file-like object is returned.  This supports the following methods:
 \method{read()}, \method{readline()}, \method{readlines()}, \method{fileno()},
 \method{close()}, \method{info()} and \method{geturl()}.  It also has
 proper support for the iterator protocol.
+One caveat: the \method{read()} method, if the size argument is
+omitted or negative, may not read until the end of the data stream;
+there is no good way to determine that the entire stream from a socket
+has been read in the general case.
 
 Except for the \method{info()} and \method{geturl()} methods,
 these methods have the same interface as for