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 techtonik
Recipients BitTorment, Yaniv.Aknin, alanmcintyre, brtzsnr, georg.brandl, techtonik
Date 2010-04-08.07:51:53
SpamBayes Score 1.63825e-08
Marked as misclassified No
Message-id <1270713115.42.0.239677469321.issue2824@psf.upfronthosting.co.za>
In-reply-to
Content
On the second thought having a switch for a low-level zip format hacking is a good addition. It may also be used for in-place removals from .zip file by erasing directory entry. Otherwise remove operation will require repacking archive into temporary file, which is too high level and vulnerable to disk space/permission matters.

So, I vote for:
(b) a switch in ZipFile's __init__() that will raise by default
and also because you'd need to modify write() and writestr().

class zipfile.ZipFile(file[, mode[, compression[, allowZip64, [low_level]]]]) 

"""Added in version 2.7: If `low_level` compatibility switch is set (False by default), then ZipFile allows low level operations, such as adding two files with the same name without raising an exception. This is for compatibility with previous versions.""" 

BTW, allowZip64 would be nice to be aliased/deprecated in favor of allow_zip64 for consistency with other double word params in module.
History
Date User Action Args
2010-04-08 07:51:56techtoniksetrecipients: + techtonik, georg.brandl, alanmcintyre, BitTorment, brtzsnr, Yaniv.Aknin
2010-04-08 07:51:55techtoniksetmessageid: <1270713115.42.0.239677469321.issue2824@psf.upfronthosting.co.za>
2010-04-08 07:51:53techtoniklinkissue2824 messages
2010-04-08 07:51:53techtonikcreate