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 lars.gustaebel
Recipients Thomas Güttler, ethan.furman, guettli, lars.gustaebel, martin.panter
Date 2015-05-28.09:03:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432803823.81.0.93834702794.issue24259@psf.upfronthosting.co.za>
In-reply-to
Content
@Martin:

Yes, that's right, but only for cases where the TarFile.fileobj attribute is an actual file object. But, most of the time it is something special, e.g. GzipFile or sys.stdin, which makes random seeking either impossible or perform very badly.

But thanks for your objection, I have to withdraw the statement I made under option 2.: compressed archives are much more common than uncompressed ones. We probably wouldn't lose too much if we no longer use seek() but read() in TarFile.next(). Reading in an uncompressed file is fast anyway. I have to think about this.
History
Date User Action Args
2015-05-28 09:03:43lars.gustaebelsetrecipients: + lars.gustaebel, guettli, ethan.furman, martin.panter, Thomas Güttler
2015-05-28 09:03:43lars.gustaebelsetmessageid: <1432803823.81.0.93834702794.issue24259@psf.upfronthosting.co.za>
2015-05-28 09:03:43lars.gustaebellinkissue24259 messages
2015-05-28 09:03:43lars.gustaebelcreate