#22895: [PEP8] Acronyms in class names should be uppercase
-------------------------------------+-------------------------------------
Reporter: bendavis78 | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: master
Component: Uncategorized | Resolution:
Severity: Normal | Triage Stage:
Keywords: | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timo):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Please post to the mailing list about this. As it will probably affect 99%
of projects, it's definitely not a decision to be taken lightly. While
updating is probably a simple find/replace for most people, anyone who
wants to support Django 2.0 (when the old versions would be dropped) as
well as Django 1.7 (before the new versions would be added) will need to
add a lot of try/except to handle both import styles. I'm not convinced
purity beats practicality in this case.
--
Ticket URL: <https://code.djangoproject.com/ticket/22895#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.5d78b1c0272bebe3b57477030d2e616d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
