Message52077
I've modified ZipFile.getinfo to raise a KeyError instead of a RuntimeError. It would appear that RuntimeError is what stuff in this module raises for IO problems, so I'm assuming this means we're stuck with it (even though I agree that IOError would seem more appropriate for trying to write to closed files).
I documented some of the exceptions raised by various methods. However, I focused mainly on the items listed in my original post, so there's probably code that raise exceptions that still aren't properly documented.
I also noticed that the existing docs list "error" as the exception that is raised for bad zip files. Since no such exception is raised, I included a change to the docs so that it says BadZipfile instead.
I included a change to the NEWS file as well, since it was mentioned in py-dev discussion that such updates can be helpful. :-)
File Added: zipfile_coverage2.diff |
|
| Date |
User |
Action |
Args |
| 2007-08-23 15:57:00 | admin | link | issue1675424 messages |
| 2007-08-23 15:57:00 | admin | create | |
|