#32621: class names might follow pep8
-------------------------------------+-------------------------------------
Reporter: BeryCZ | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Uncategorized | Version: 3.2
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by BeryCZ:
Old description:
> Hi,
> I've noticed that some class names don't follow pep 8 and it's quite
> annoying to either remember or search for the right name.
> What comes to mind rn is `JsonResponse` (which is ok) and classes like
> `JSONField`, `JSONCatalog`, `JSONString` and some more.
> Would be nice to change the class names some time to `Json` and for
> backward compatibility do `JSONField = JsonField`
New description:
Hi,
I've noticed that some class names don't follow pep 8 and it's quite
annoying to either remember or search for the right name.
What comes to mind rn is `JsonResponse` (which is ok) and classes like
`JSONField`, `JSONCatalog`, `JSONString` and some more.
Would be nice to change the class names some time to `Json` and for
backward compatibility to do `JSONField = JsonField`
--
--
Ticket URL: <https://code.djangoproject.com/ticket/32621#comment:2>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.8682f181723d1574be864173feb1d3c1%40djangoproject.com.
