Message 378934 - Python tracker

➜

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	jan.schatz
Recipients	jan.schatz
Date	2020-10-19.08:55:37
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1603097737.92.0.915813500773.issue42079@roundup.psfhosted.org>
In-reply-to

Content
I have a tar gz archive that fails to be extracted via tarfile.extractall(). By adding some debug code I found that at some point InvalidHeaderError is raised inside tarfile.next(). But the function just swallows the exception, because the offset isn't 0 (see https://github.com/python/cpython/blob/5368c2b6e23660cbce7e38dc68f859c66ac349ee/Lib/tarfile.py#L2334). Why does the function behave like this? I would expect an except rather than silently stopping extraction if the archive is damaged.

I have a tar gz archive that fails to be extracted via tarfile.extractall(). By adding some debug code I found that at some point InvalidHeaderError is raised inside tarfile.next(). But the function just swallows the exception, because the offset isn't 0 (see https://github.com/python/cpython/blob/5368c2b6e23660cbce7e38dc68f859c66ac349ee/Lib/tarfile.py#L2334). Why does the function behave like this? I would expect an except rather than silently stopping extraction if the archive is damaged.

History
Date	User	Action	Args
2020-10-19 08:55:37	jan.schatz	set	recipients: + jan.schatz
2020-10-19 08:55:37	jan.schatz	set	messageid: <1603097737.92.0.915813500773.issue42079@roundup.psfhosted.org>
2020-10-19 08:55:37	jan.schatz	link	issue42079 messages
2020-10-19 08:55:37	jan.schatz	create