Message160684
| Author | meador.inge |
|---|---|
| Recipients | alanmcintyre, eric.araujo, loewis, mark.dickinson, meador.inge, pleed, serhiy.storchaka, terry.reedy, ubershmekel |
| Date | 2012-05-15.05:24:04 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1337059445.61.0.940285409745.issue14315@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
> I would still like to see the zipfile module to be able to detect > ill-formed zipfiles - certainly not by default. Agreed. We already do produce some informational messages via the documented 'ZipFile.debug' attribute. Just checking that flag and producing a message to stdout like we do in other cases is one option. Another, as you suggested already, is to provide a strict flag that indicates an exception should be thrown upon encountering an ill-formed file. I like the idea of reusing what we already have. Although, when it fails, it doesn't fail loudly. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-05-15 05:24:05 | meador.inge | set | recipients: + meador.inge, loewis, terry.reedy, mark.dickinson, alanmcintyre, eric.araujo, ubershmekel, serhiy.storchaka, pleed |
| 2012-05-15 05:24:05 | meador.inge | set | messageid: <1337059445.61.0.940285409745.issue14315@psf.upfronthosting.co.za> |
| 2012-05-15 05:24:05 | meador.inge | link | issue14315 messages |
| 2012-05-15 05:24:04 | meador.inge | create | |