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 stutzbach
Recipients benjamin.peterson, pitrou, stutzbach
Date 2010-09-28.15:19:00
SpamBayes Score 2.4790003e-11
Marked as misclassified No
Message-id <1285687142.56.0.374488173842.issue9971@psf.upfronthosting.co.za>
In-reply-to
Content
The readinto() method is intended to offer better performance than read() by allowing the caller to read into a preallocated buffer rather than constantly allocate and deallocate buffers.

However, bufferediobase_readinto() calls read(), so the extra allocations and deallocations happen anyway.  On a related note, buffered_readinto() has a comment reading "TODO: use raw.readinto() instead!" which should be explored.

I can write a patch for this, but it will probably be awhile before I get to it.  Anyone else who feels inspired should feel free to write one. :-)
History
Date User Action Args
2010-09-28 15:19:02stutzbachsetrecipients: + stutzbach, pitrou, benjamin.peterson
2010-09-28 15:19:02stutzbachsetmessageid: <1285687142.56.0.374488173842.issue9971@psf.upfronthosting.co.za>
2010-09-28 15:19:00stutzbachlinkissue9971 messages
2010-09-28 15:19:00stutzbachcreate