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.
This commit is contained in:
parent
267b062432
commit
504ca68e20
|
@ -29,6 +29,10 @@ file-like object is returned. This supports the following methods:
|
||||||
\method{read()}, \method{readline()}, \method{readlines()}, \method{fileno()},
|
\method{read()}, \method{readline()}, \method{readlines()}, \method{fileno()},
|
||||||
\method{close()}, \method{info()} and \method{geturl()}. It also has
|
\method{close()}, \method{info()} and \method{geturl()}. It also has
|
||||||
proper support for the iterator protocol.
|
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,
|
Except for the \method{info()} and \method{geturl()} methods,
|
||||||
these methods have the same interface as for
|
these methods have the same interface as for
|
||||||
|
|
Loading…
Reference in New Issue