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 Arfrever, Matt.Mackall, alanmcintyre, benjamin.peterson, durin42, dw, eric.araujo, kasal, larry, loewis, mcepl, ocean-city, pitrou, python-dev, r.david.murray, serhiy.storchaka
Date 2015-01-16.19:35:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1421436905.56.0.840510311054.issue14099@psf.upfronthosting.co.za>
In-reply-to
Content
Thank you for your report Matt.

There is other problem. It is nowhere documented and newer granted and newer mentioned when ZipFile.open() was added, but file-like objects returned by ZipFile.open() could be read in different threads simultaneously. It makes sense because decompressors release GIL and parallel reading compressed file can has benefit.

It is easy to fix both issues (I prefer to do this in separate paths), but due to the overall complexity it is safer to withdraw committed changes in maintained releases and apply additional patches only in default branch.
History
Date User Action Args
2015-01-16 19:35:05serhiy.storchakasetrecipients: + serhiy.storchaka, loewis, alanmcintyre, pitrou, ocean-city, larry, benjamin.peterson, mcepl, durin42, eric.araujo, Arfrever, r.david.murray, python-dev, Matt.Mackall, kasal, dw
2015-01-16 19:35:05serhiy.storchakasetmessageid: <1421436905.56.0.840510311054.issue14099@psf.upfronthosting.co.za>
2015-01-16 19:35:05serhiy.storchakalinkissue14099 messages
2015-01-16 19:35:05serhiy.storchakacreate