#32621: class names might follow pep8
-------------------------------------+-------------------------------------
Reporter: BeryCZ | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Core (Other) | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
* component: Uncategorized => Core (Other)
Comment:
Thanks for this proposition.
> What comes to mind rn is JsonResponse (which is ok) and classes like
JSONField, JSONCatalog, JSONString and some more.
I would rather do the opposite, as suggested in #22895 and as we did for a
new API, e.g. `ASGIRequest`, `ASGIHandler`. Nonetheless, it's not worth to
change an existing API.
--
Ticket URL: <https://code.djangoproject.com/ticket/32621#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.e98fdf14c6da734f1cb2d8772b316d9f%40djangoproject.com.
