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 gregory.p.smith
Recipients alanmcintyre, eric.araujo, gregory.p.smith, loewis, mark.dickinson, meador.inge, pleed, python-dev, serhiy.storchaka, terry.reedy, ubershmekel, void.sender
Date 2014-05-30.06:59:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1401433178.08.0.596227633045.issue14315@psf.upfronthosting.co.za>
In-reply-to
Content
This was never an enhancement.  zipfile was failing to properly deal with real world data that other zip file tools on the planet were perfectly happy to deal with.  That's a bug.  Fixed.

 Practicality beats purity.
 Be lenient in what you accept.

The zipfile module is not meant to be a zip "standard" validation tool.

The other discussions in this bug about adding actual features such as a "strict" mode flag could be done but should really go in feature requests of their own.  The zipfile module is... not a wonderful body of code (understatement).  Example: It is still quite possible to get non zipfile.BadZipFile exceptions such as struct.error based on various arrangements of input data.
History
Date User Action Args
2014-05-30 06:59:38gregory.p.smithsetrecipients: + gregory.p.smith, loewis, terry.reedy, mark.dickinson, alanmcintyre, eric.araujo, ubershmekel, meador.inge, python-dev, serhiy.storchaka, pleed, void.sender
2014-05-30 06:59:38gregory.p.smithsetmessageid: <1401433178.08.0.596227633045.issue14315@psf.upfronthosting.co.za>
2014-05-30 06:59:37gregory.p.smithlinkissue14315 messages
2014-05-30 06:59:36gregory.p.smithcreate