#22895: [PEP8] Acronyms in class names should be uppercase
-------------------------------------+-------------------------------------
Reporter: bendavis78 | Owner: nobody
Type: | Status: closed
Cleanup/optimization | Version: master
Component: Uncategorized | Resolution: wontfix
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 claudep):
* status: new => closed
* resolution: => wontfix
Comment:
Replying to [comment:3 valberg]:
> Backwards incompatiability will be inevitable with Django 2.0 (as far as
I know at least).
No, unless absolutely required, I don't think we plan bigger
incompatibility issues than for other releases, hopefully!
I will raise my -1 flag for this. But as Tim said, you can try to get
support on the developers mailing list, and reopen if you get some
consensus.
--
Ticket URL: <https://code.djangoproject.com/ticket/22895#comment:4>
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.f43df638684aa7a4ea6b3893b54da409%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
