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 takluyver
Recipients Dhiraj_Mishra, martin.panter, mbussonn, python-dev, serhiy.storchaka, socketpair, takluyver
Date 2016-04-06.00:16:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Sorry for the delay, this fell off my radar because emails from both the bug tracker and Rietveld tend to fall foul of my spam filters, so I have to go and check.

I have implemented Serhiy's suggestions, but there turns out to be a test (test_write_after_read) that calls writestr while a reading handle is open, and it now fails. This is absolutely expected according to the design we discussed, but if there's a test, I guess that means we need to keep that functionality working?

In principle, the only thing that's not possible is interleaving writes to multiple files within the zip - because we don't know where to start writing the second file. We should be able to have one writer and n readers going at once, but every time I start looking into that I get mired in complexity. Maybe (hopefully) there's some critical abstraction that hasn't occurred to me.
Date User Action Args
2016-04-06 00:16:54takluyversetrecipients: + takluyver, socketpair, python-dev, martin.panter, serhiy.storchaka, mbussonn, Dhiraj_Mishra
2016-04-06 00:16:53takluyversetmessageid: <>
2016-04-06 00:16:52takluyverlinkissue26039 messages
2016-04-06 00:16:49takluyvercreate