➜

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 pitrou
Recipients nirai, pitrou
Date 2010-10-01.11:58:00
SpamBayes Score 0.0012299839
Marked as misclassified No
Message-id <1285934278.3188.3.camel@localhost.localdomain>
In-reply-to <1285933167.12.0.802819268956.issue9962@psf.upfronthosting.co.za>
Content 
> Right, I missed the change from self.max_read_chunk to 1024
> (read_size). Should not peek() limit to self.max_read_chunk as read()
> does?

This is used for the chunking of huge reads, but for peek():
1) there is no chunking (peek() should do at most one raw read)
2) huge reads are not really the use case peek() is intended for
History
Date User Action Args
2010-10-01 11:58:02pitrousetrecipients: + pitrou, nirai
2010-10-01 11:58:00pitroulinkissue9962 messages
2010-10-01 11:58:00pitroucreate