John Admanski added the comment:
I'm not sure that's much of an improvement on the existing behavior, though; as
I mentioned you can already work around it by killing all the references to the
ZipExtFile and the underlying file object will get automatically closed if the
ZipExtF
New submission from John Admanski :
When creating a ZipExtFile through ZipFile.open, the if the original ZipFile
object was created with a filename then a new file object will be opened and
given to the ZipExtFile to use for its file operations. There is no explicit
mechanism that will allow
