#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
-------------------------------------+-------------------------------------
Comment (by valberg):
Backwards incompatiability will be inevitable with Django 2.0 (as far as I
know at least). So I suspect that this wouldn't be the only situation
where try/except would be required if you want to support Django <2.0 AND
2.x.
That said if we want to adhere to PEP8 in this case, why shouldn't we also
do that in other cases (like max 79 character line limit)? It would
require quite a big overhaul of the code base though :)
Bottom line: I'm a big fan of PEP8 because it sets a baseline for code
maintainability - but as timo says, this is more of a purity vs.
practicality issue than pro/con PEP8.
--
Ticket URL: <https://code.djangoproject.com/ticket/22895#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.af6a4e2ae780477c3fc4250e1ec6a0dc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
