Opened 4 years ago
Closed 4 years ago
#32621 closed Cleanup/optimization (wontfix)
class names might follow pep8
| Reported by: | BeryCZ | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | 3.2 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
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
Change History (3)
comment:1 by , 4 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 4 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 4 years ago
| Component: | Uncategorized → Core (Other) |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Thanks for this proposition.
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.