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 alexandre.vassalotti
Recipients alexandre.vassalotti, amaury.forgeotdarc, collinwinter, hagen, pitrou, vstinner
Date 2009-04-08.17:28:03
SpamBayes Score 7.868076e-07
Marked as misclassified No
Message-id <>
Victor, Unpickler shouldn't raise an error if the given file object does
support seek(); it should gracefully fall back to using only read() and
readline(). Also, I think you could get a greater performance
improvement by using peek() and avoiding backward seeks. As far as I
know, a backward seek may invalidate the internal buffer of the file
object, thus forcing a read from disk.

Incidentally, I think it would be nice to add to Python 3 some kind of
file protocol as this would provide a way to mitigate the function call
overhead for I/O operations.
Date User Action Args
2009-04-08 17:28:07alexandre.vassalottisetrecipients: + alexandre.vassalotti, collinwinter, amaury.forgeotdarc, pitrou, vstinner, hagen
2009-04-08 17:28:07alexandre.vassalottisetmessageid: <>
2009-04-08 17:28:05alexandre.vassalottilinkissue3873 messages
2009-04-08 17:28:04alexandre.vassalotticreate