Boštjan Mejak bostjan.me...@gmail.com added the comment:
I'm reopening this and I am making it a feature request for Python 3.2
--
components: +Interpreter Core -Documentation
resolution: wont fix -
status: closed - open
type: - feature request
versions: -Python 2.6, Python 2.7,
Changes by Georg Brandl ge...@python.org:
--
assignee: georg.brandl -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7351
___
___
Python-bugs-list
Changes by Georg Brandl ge...@python.org:
--
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7351
___
___
Python-bugs-list
Changes by Éric Araujo mer...@netwok.org:
--
resolution: fixed - wont fix
stage: - committed/rejected
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7351
___
Éric Araujo mer...@netwok.org added the comment:
Your patch need to include an alias (BadZipfile = BadZipFile) to
preserve compatibility with old pickles, as explains msg95477.
Cheers
--
nosy: +Merwok
___
Python tracker rep...@bugs.python.org
Antoine Pitrou pit...@free.fr added the comment:
While the mismatched casing is unfortunate, I don't think changing it
for the sake of aesthetics is a good deal given that many existing
programs will have to be converted to the new spelling.
--
nosy: +pitrou
Retro vinet...@gmail.com added the comment:
I suggest renaming the class from BadZipfile to BadZipFile. We have a
class named LargeZipFile. It would make sence to have the previously
mentioned class named as BadZipFile then. What is your verdict on that?
--
Ezio Melotti ezio.melo...@gmail.com added the comment:
The old name could be deprecated and replaced by the right one, but as
Eric Smith mentioned on #python-dev, the class with the old name can't
be removed because - even if unlikely - the object might exist in a pickle.
So we can either live
Retro vinet...@gmail.com added the comment:
I am merely speaking of renaming the class name from BadZipfile to
BadZipFile.
class BadZipFile(exceptions.Exception):
# etc.
Only the name is fixed at class definition. I am aiming for that in this
bug report. And then every other BadZipfile
Ezio Melotti ezio.melo...@gmail.com added the comment:
It might be doable for Python and its stdlib, but all the programs and
modules that are using the old name will start raising errors if they
don't find the old name anymore.
If the old name is deprecated for at least one Python version (e.g.
Retro vinet...@gmail.com added the comment:
I made a patch which fixes the BadZipfile issue. Please take a look and
decide whether you'll toss it or use it. Maybe it'll come handy some
other time in the future.
--
keywords: +patch
Added file:
New submission from Retro vinet...@gmail.com:
There are some minor typos in the docs. The section zipfile has twp typos:
exception zipfile.BadZipfile
The error raised for bad ZIP files (old name: zipfile.error).
this should be
exception zipfile.BadZipFile
The error raised for bad ZIP
Georg Brandl ge...@python.org added the comment:
BadZipfile is actually the correct name of the exception.
Fixed the other nit in r76376.
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
Retro vinet...@gmail.com added the comment:
Thanks for upcassing 'Python'.
I have to ask you why are all other classes named in the form of
...ZipFile, like
- exception: LargeZipFile
- class: ZipFile
- class: PyZipFile
Please at least consider of making the class BadZipfile consistent to
other
14 matches
Mail list logo
