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 serhiy.storchaka
Recipients alanmcintyre, eric.araujo, loewis, mark.dickinson, meador.inge, pleed, serhiy.storchaka, terry.reedy, ubershmekel
Date 2012-05-13.18:27:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1336933783.3172.295.camel@raxxla>
In-reply-to <1336931933.83.0.17014569472.issue14315@psf.upfronthosting.co.za>
Content
> I can sympathize with the desire to accept the zipfile, anyway (i.e. despite it being broken). At the same time, I also think that Python should not let errors pass silently.

I do not know other implementation of ZIP, which output an error or a
warning on such files. The fact is that such files exist in the wild
world.

> So as a way out, I propose that the ZipFile class gains a "strict" attribute, indicating whether "acceptable" violations of the spec are ignored or reported as exceptions.

It is a not easy task (and unnecessary, I suppose). Now zipfile ignores
many errors (for example, it completely ignores local file headers).
History
Date User Action Args
2012-05-13 18:27:07serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, terry.reedy, mark.dickinson, alanmcintyre, eric.araujo, ubershmekel, meador.inge, pleed
2012-05-13 18:27:06serhiy.storchakalinkissue14315 messages
2012-05-13 18:27:06serhiy.storchakacreate