Opened 16 hours ago
Last modified 6 hours ago
#36266 assigned Cleanup/optimization
HIDE_PRODUCTION_WARNING variable name is ambiguous
Description ¶
Hi - I just saw this feature in the 5.2 release candidate docs, hopefully this isn't too late.
Could the env variable name could be changed from HIDE_PRODUCTION_WARNING
to something that's Django specific, ie. DJANGO_HIDE_PRODUCTION_WARNING
?
That would align the name with a lot of the other env variable names that Django uses and would reduce potential confusion for an unfamiliar engineer seeing the env variable name being set.
According to the ticket's flags, the next step(s) to move this issue forward are:
- For anyone except the patch author to review the patch using the patch review checklist and either mark the ticket as "Ready for checkin" if everything looks good, or leave comments for improvement and mark the ticket as "Patch needs improvement".
Change History (7)
comment:1 by , 16 hours ago
Cc: | added |
---|---|
Severity: | Normal → Release blocker |
Triage Stage: | Unreviewed → Accepted |
comment:2 by , 16 hours ago
Even more explicit could be something like DJANGO_RUNSERVER_HIDE_PRODUCTION_WARNING
. That would make it very clear that it's only a variable for the management command - but that may be too long of a name?
comment:3 by , 15 hours ago
I agree with the rationale and with the ticket acceptance. My proposal would be to use: DJANGO_RUNSERVER_HIDE_WARNING
(since I don't think the PRODUCTION
provides any extra information here and to me it feels a bit confusing).
comment:4 by , 15 hours ago
This all sounds reasonable, if I remember correctly the original name matches the command line flag, which I don't think needs to change in this case?
comment:5 by , 7 hours ago
Owner: | set to |
---|---|
Status: | new → assigned |
comment:6 by , 6 hours ago
Has patch: | set |
---|
I think I agree here, other env vars include
DJANGO_SETTINGS_MODULE
,DJANGO_COLORS
,DJANGO_SUPERUSER_PASSWORD
,DJANGO_WATCHMAN_TIMEOUT
,DJANGO_ALLOW_ASYNC_UNSAFE
.