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, georg.brandl, larry, serhiy.storchaka
Date 2014-01-14.20:56:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1389732995.51.0.822070396354.issue20262@psf.upfronthosting.co.za>
In-reply-to
Content
When ZipFile.debug is not zero, some debugging messages are printed to stdout. Some of them are for debugging the zipfile module itself. But some are warnings about user's operation which perhaps make not what the user is expected -- truncating long archive comment or adding a file with duplicated name. These cases cases can be considered as logic error, they can be prevented by external checks (check that comment's length does not excite the limit and that specified name is not in the ZIP file). So it will be sane and helpful to convert these prints to regular warnings, which are controlled in same way as all other warnings.

See also issue2824. It have a patch which looks too excessive to me.

Here is a patch. I don't sure to which version it should be targeted.
History
Date User Action Args
2014-01-14 20:56:35serhiy.storchakasetrecipients: + serhiy.storchaka, georg.brandl, alanmcintyre, larry
2014-01-14 20:56:35serhiy.storchakasetmessageid: <1389732995.51.0.822070396354.issue20262@psf.upfronthosting.co.za>
2014-01-14 20:56:35serhiy.storchakalinkissue20262 messages
2014-01-14 20:56:35serhiy.storchakacreate