Opened 9 years ago
Closed 9 years ago
#27376 closed Cleanup/optimization (invalid)
Why not use plural format MIDDLEWARES in settings.py in Django 1.10.x
| Reported by: | WeizhongTu | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | 1.10 |
| Severity: | Normal | Keywords: | MIDDLEWARE |
| 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 )
I know that we can implement a middleware using a function and a class in Django 1.10.x, so the related setting was renamed from "MIDDLEWARE_CLASSES" to "MIDDLEWARE".
In settings.py ALLOWED_HOSTS, INSTALLED_APPS,TEMPLATES,DATABASES are plural formats.
My question is Why NOT use "MIDDLEWARES" (plural format)?
Change History (3)
comment:1 by , 9 years ago
| Summary: | Why Django 1.10.x not use plural format in settings.py → Why not use plural format MIDDLEWARES in settings.py in Django 1.10.x |
|---|
comment:2 by , 9 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 9 years ago
| Component: | Uncategorized → Core (Other) |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
This came up during the feature design, but actually
MIDDLEWAREis both singular and plural.