This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author raz
Recipients georg.brandl, raz
Date 2008-09-12.19:05:42
SpamBayes Score 2.21243e-06
Marked as misclassified No
Message-id <1221246343.23.0.128587140594.issue3849@psf.upfronthosting.co.za>
In-reply-to
Content
The documentation for urllib.urlopen() states:

"One caveat: the 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."

To an innocent reader this effectively translates to:
"The read() method may silently truncate your data but we won't tell you
any details about it."

The paragraph should be clarified as follows:

- Under what circumstances can truncation happen (which protocols are
affected, under which conditions?)
- What are safe use-cases where truncation can not happen (e.g. the
common case of a simple HTTP-GET)
History
Date User Action Args
2008-09-12 19:05:43razsetrecipients: + raz, georg.brandl
2008-09-12 19:05:43razsetmessageid: <1221246343.23.0.128587140594.issue3849@psf.upfronthosting.co.za>
2008-09-12 19:05:42razlinkissue3849 messages
2008-09-12 19:05:42razcreate