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 vinay.sajip
Recipients Arfrever, amaury.forgeotdarc, benjamin.peterson, georg.brandl, vinay.sajip
Date 2011-06-09.19:50:07
SpamBayes Score 3.908224e-05
Marked as misclassified No
Message-id <1307649007.96.0.413872087946.issue12291@psf.upfronthosting.co.za>
In-reply-to
Content
Another thought about buffering, which might be a bit of a show-stopper: if in a particular load() call we read ahead for buffering purposes, we've altered the underlying stream (which might not be seekable to allow position restoring). The next call to load() will be likely to fail, since the underlying stream has been positioned further than expected by the earlier load() call, and the buffer state has been lost. Not sure how easy it is to get around this ...
History
Date User Action Args
2011-06-09 19:50:08vinay.sajipsetrecipients: + vinay.sajip, georg.brandl, amaury.forgeotdarc, benjamin.peterson, Arfrever
2011-06-09 19:50:07vinay.sajipsetmessageid: <1307649007.96.0.413872087946.issue12291@psf.upfronthosting.co.za>
2011-06-09 19:50:07vinay.sajiplinkissue12291 messages
2011-06-09 19:50:07vinay.sajipcreate