➜

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 BreamoreBoy, alexandre.vassalotti, amaury.forgeotdarc, belopolsky, collinwinter, hagen, pitrou, vstinner
Date 2010-09-27.22:06:35
SpamBayes Score 2.677481e-06
Marked as misclassified No
Message-id <1285625191.10095.5.camel@localhost.localdomain>
In-reply-to <AANLkTinUg=1r6ashosG5p5T7fR2jhOtTsu=E-=BUB+jR@mail.gmail.com>
Content 
> Didn't Victor say that only one seek at the end is necessary per
> pickle? If this is the case, I don't think expensive seeks will be an
> issue.

If you are unpickling from a multi-megabyte gzip file and the seek at
the end makes you uncompress all the gzip file again, it can certainly
be a problem.

Another issue with seeking only at the end is that it would make
readline() quite more complicated. And, apparently, readline() is not
only used on protocol 0 but also on binary protocols.
History
Date User Action Args
2010-09-27 22:06:37pitrousetrecipients: + pitrou, collinwinter, amaury.forgeotdarc, belopolsky, vstinner, alexandre.vassalotti, hagen, BreamoreBoy
2010-09-27 22:06:35pitroulinkissue3873 messages
2010-09-27 22:06:35pitroucreate