Brian Curtin cur...@acm.org added the comment:
Since the issue exists in 2.6 and is only currently fixed on trunk and
beyond, shouldn't the 6511 fix make it's way backwards into 2.6.x?
--
nosy: +brian.curtin
___
Python tracker rep...@bugs.python.org
skelker steve.kel...@dtn.com added the comment:
That would be great. Perhaps that should be discussed in 6511. I'll make a
note there.
Steve Kelker
(952)882-4381 (or x4381)
--
___
Python tracker rep...@bugs.python.org
Ryan Leslie ryle...@gmail.com added the comment:
Yes, I think this fix should have been included in the 2.6 branch. I
subscribed Amaury to look into that when I last updated.
--
___
Python tracker rep...@bugs.python.org
R. David Murray rdmur...@bitdance.com added the comment:
The 2.6 branch was frozen except for critical issues during the release
process for 2.6.3 and then 2.6.4. Now that 2.6.4 is out, the bug fix
can be backported.
--
nosy: +r.david.murray
___
Ryan Leslie ryle...@gmail.com added the comment:
I expect this should already be fixed by the commit in
http://bugs.python.org/issue6511
BadZipFile will now be raised for empty files rather than IOError, and
so ZipFile._GetContents() should now also close the file.
The fix was committed to
skelker steve.kel...@dtn.com added the comment:
Thanks. I did do a search before opening my ticket. Not sure why I didn't see
that in my search. Sorry for the duplicate ticket.
Steve Kelker
(952)882-4381 (or x4381)
--
___
Python tracker
skelker steve.kel...@dtn.com added the comment:
Fixed in http://bugs.python.org/issue6511
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7169
___
New submission from skelker steve.kel...@dtn.com:
I noticed today if I attempt to create a ZipFile object for read access,
and the zip file is zero bytes, the ZipFile object throws an exception,
but there is still an open handle to the file. So if I catch that
exception, and then try to delete
