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 JieGhost, lars.gustaebel, r.david.murray, rhettinger, socketpair
Date 2016-07-28.06:42:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1469688174.66.0.558714821416.issue27590@psf.upfronthosting.co.za>
In-reply-to
Content
After all these years, it is not that easy to say why the decision to swallow this exception was made. One part surely was a lack of experience with the tar format itself and all of its implementations. The other part I guess was that it was supposed to avoid problems in case users did not use TarFile as an iterator. tarfile was developed on Python 2.2 which was the first release to feature iterators. The problem if you do random access on a tarfile or call TarFile.getmembers() is that first of all all the headers must be collected. If this fails somewhere in the middle, there is no way to resume the current operation and you get nothing out of the archive.
History
Date User Action Args
2016-07-28 06:42:54lars.gustaebelsetrecipients: + lars.gustaebel, rhettinger, r.david.murray, socketpair, JieGhost
2016-07-28 06:42:54lars.gustaebelsetmessageid: <1469688174.66.0.558714821416.issue27590@psf.upfronthosting.co.za>
2016-07-28 06:42:54lars.gustaebellinkissue27590 messages
2016-07-28 06:42:54lars.gustaebelcreate