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 ncoghlan
Recipients benjamin.peterson, conf, ncoghlan, pitrou, trott
Date 2009-06-14.01:12:25
SpamBayes Score 1.860102e-08
Marked as misclassified No
Message-id <1244941949.2.0.22046055893.issue5811@psf.upfronthosting.co.za>
In-reply-to
Content
It's not the docstring that is wrong for the current behaviour, it's the
IO.BufferedReader documentation:

"""
peek([n])
    Return 1 (or n if specified) bytes from a buffer without advancing
the position. Only a single read on the raw stream is done to satisfy
the call. The number of bytes returned may be less than requested since
at most all the buffer’s bytes from the current position to the end are
returned.
"""

That gives absolutely no indication that the call might return more
bytes than expected, and the indication that leaving out the argument
will return only the next byte is flat out wrong.
History
Date User Action Args
2009-06-14 01:12:30ncoghlansetrecipients: + ncoghlan, pitrou, benjamin.peterson, trott, conf
2009-06-14 01:12:29ncoghlansetmessageid: <1244941949.2.0.22046055893.issue5811@psf.upfronthosting.co.za>
2009-06-14 01:12:27ncoghlanlinkissue5811 messages
2009-06-14 01:12:26ncoghlancreate