HIDE_PRODUCTION_WARNING variable name is ambiguous

[Leo]

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.

[Sarah Boyce]

I think I agree here, other env vars include DJANGO_SETTINGS_MODULE, DJANGO_COLORS, DJANGO_SUPERUSER_PASSWORD, DJANGO_WATCHMAN_TIMEOUT, DJANGO_ALLOW_ASYNC_UNSAFE.

[Leo]

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?

[Natalia Bidart]

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).

[Andy Miller]

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?

[Johanan Oppong Amoateng]

​https://github.com/django/django/pull/19287

[Sarah Boyce <42296566+sarahboyce@…>]

In 5adadf6:

Fixed #36266 -- Renamed HIDE_PRODUCTION_WARNING environment variable to DJANGO_RUNSERVER_HIDE_WARNING.

[Sarah Boyce <42296566+sarahboyce@…>]

In 321a5651:

[5.2.x] Fixed #36266 -- Renamed HIDE_PRODUCTION_WARNING environment variable to DJANGO_RUNSERVER_HIDE_WARNING.

Backport of 5adadf6e8c74ab14d432e9d682ca1914789386de from main.