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 kasal
Recipients alanmcintyre, jcea, kasal, serhiy.storchaka
Date 2012-12-03.16:03:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354550606.68.0.517382332475.issue16569@psf.upfronthosting.co.za>
In-reply-to
Content
I agree that reading from a file open for write should be forbidden, no matter whether ZipFile was called with fp or a name.

Actually, it is not yet forbidden, and two of the tests in the zipfile.py test suite do actually rely on this misfeature.
The first chunk in the patch http://bugs.python.org/file24624/Proposed-fix-of-issue14099-second.patch contains a fix for this bug in test suite.

OTOH, decompressing several files for a given zip file simultaneously does not sound that bad.  You know, with all the current file managers, people look at a zip as if it were kind of a directory.
History
Date User Action Args
2012-12-03 16:03:26kasalsetrecipients: + kasal, jcea, alanmcintyre, serhiy.storchaka
2012-12-03 16:03:26kasalsetmessageid: <1354550606.68.0.517382332475.issue16569@psf.upfronthosting.co.za>
2012-12-03 16:03:26kasallinkissue16569 messages
2012-12-03 16:03:26kasalcreate