Author loewis
Recipients alanmcintyre, eric.araujo, loewis, mark.dickinson, meador.inge, pleed, serhiy.storchaka, terry.reedy, ubershmekel
Date 2012-05-13.19:03:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <4FB00589.5010006@v.loewis.de>
In-reply-to <1336933783.3172.295.camel@raxxla>
Content
>> 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).

Why do you consider this difficult? Just add a "strict" flag, make
it false by default, and raise an error if there is any unparsable
extra data.

I'm not asking that you implement a complete validity check for all
aspects of the zip spec - just that there is a mode where it continues
to raise an exception as it currently does (but with a better
exception).
History
Date User Action Args
2012-05-13 19:03:39loewissetrecipients: + loewis, terry.reedy, mark.dickinson, alanmcintyre, eric.araujo, ubershmekel, meador.inge, serhiy.storchaka, pleed
2012-05-13 19:03:38loewislinkissue14315 messages
2012-05-13 19:03:38loewiscreate