-
-
Notifications
You must be signed in to change notification settings - Fork 29.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename BadZipfile to BadZipFile for consistency #51600
Comments
There are some minor typos in the docs. The section zipfile has twp typos: exception zipfile.BadZipfile this should be exception zipfile.BadZipFile Note: There needs to be a capital F in the exception class name BadZipFile. There's also a typo in the sentence "Decryption is extremely slow as it Note: The word 'python' is needed to be capitalized. These typos exist since the creation of the zipfile docs. Please correct |
BadZipfile is actually the correct name of the exception. Fixed the other nit in r76376. |
Thanks for upcassing 'Python'. I have to ask you why are all other classes named in the form of
Please at least consider of making the class BadZipfile consistent to |
I suggest renaming the class from BadZipfile to BadZipFile. We have a |
The old name could be deprecated and replaced by the right one, but as |
I am merely speaking of renaming the class name from BadZipfile to class BadZipFile(exceptions.Exception):
# etc. Only the name is fixed at class definition. I am aiming for that in this |
It might be doable for Python and its stdlib, but all the programs and |
I made a patch which fixes the BadZipfile issue. Please take a look and |
Your patch need to include an alias (BadZipfile = BadZipFile) to Cheers |
While the mismatched casing is unfortunate, I don't think changing it |
Unless we are going to add an alias for BadZipfile, I'll close this as won't fix. |
I'm reopening this and I am making it a feature request for Python 3.2 |
Boštjan, you need to update your patch to add the missing alias to the old name, as well as docs and test updates. I’m +0 on the change. |
I am -1 for the alias. I want that this gets renamed in Python 3.2, not On Wed, Oct 27, 2010 at 10:43 PM, Éric Araujo <report@bugs.python.org>wrote:
|
You may "not care" about backwards compatibility, but introducing a breaking change in 3.2 for mere style-conformity is not OK, IMO. If the patcher insists on it being a breaking change, it should be rejected. FWIW, this casing is sufficiently bizarre and inconsistent in the module itself, that it seems clearly wrong and likely to produce difficulties for people using it-- so although I'm not upgrading to Python3 anytime soon, I'd really like to change my code to be BadZipFile when I do, so I'd be +1 with an alias. :) |
No alias. Be stubborn and let the stdlib die in inconsistency. On Thu, Oct 28, 2010 at 2:11 AM, Stephen Hansen <report@bugs.python.org>wrote:
|
Considering I do use zipfiles a lot, I slightly care about this (at least, eventually)-- I'm attaching a new patch, with doc and test changes as well (and the compatibility alias). What convinced me was looking at test_zipfile, and noticing how often it actually confused the issue in comments at least, between typing BadZipfile and BadZipFile. Dunno if I worded the doc-change well, so you may want to adjust that. |
Oh: and I tested it against branches/py3k in the head, it applies cleanly and builds, and test_zipfile runs without error. |
Applied after review in r85874. (Please make sure your patches don't have trailing whitespace.) |
A “BadZipZile” in the patch made it to Subversion :) Fixed in r85891. |
Thanks for the catch! |
Is the trailing whitespace problem solved? Please make sure everything is On Thu, Oct 28, 2010 at 8:42 AM, Georg Brandl <report@bugs.python.org>wrote:
|
a) I already removed the whitespace before committing. The pre-commit hook wouldn't even allow committing that. b) I don't think constant refusal to submit a patch in the way we request earns you a place in the acknowledgements. |
(P.S. Would you be so kind as to follow some netiquette in the tracker? HTML email creates noisy unnamed attachments, and top-posting is redundant and hard to read. Thanks in advance.) |
Then disable the tracker's ability to post messages via POP/IMAP. Just block On Thu, Oct 28, 2010 at 4:05 PM, Éric Araujo <report@bugs.python.org> wrote:
|
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: