Re: [Django] #36527: Allow for runserver development server warning to be silenced via settings.

[Django]

#36527: Allow for runserver development server warning to be silenced via settings.
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: New feature | Status: closed
Component: Core (Management | Version: 5.2
commands) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):

* resolution: => wontfix
* status: new => closed

Comment:

Hello Klaas van Schelven! Thanks for the suggestion and for taking the
time to create this ticket. In general, adding new settings to Django
requires strong community consensus and clear justification. In this case,
the existing environment variable offers a reasonable workaround, and it's
not much different from defining a setting. We don't currently see a need
to introduce a dedicated setting for this, therefore I'll close the ticket
accordingly.
--
Ticket URL: <https://code.djangoproject.com/ticket/36527#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#36527: Allow for runserver development server warning to be silenced via settings.
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: New feature | Status: closed
Component: Core (Management | Version: 5.2
commands) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Klaas van Schelven):

Hmmm... there seems to be some tension between

>the existing environment variable [..] is not much different from
defining a setting

and

>adding new settings to Django requires strong community consensus and
clear justification.

also: I wonder how many of Django's behaviors are configurable via os envs
_only_ (I know of no other examples myself).

which to me suggests that it's the behavior that was implemented in 5.2
that needed the _clear justification_.

oh well...this is probably not the hill that I'll die on
--
Ticket URL: <https://code.djangoproject.com/ticket/36527#comment:3>

[Django]

#36527: Allow for runserver development server warning to be silenced via settings.
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: New feature | Status: closed
Component: Core (Management | Version: 5.2
commands) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Natalia Bidart):

Replying to [comment:3 Klaas van Schelven]:

> also: I wonder how many of Django's behaviors are configurable via os
envs _only_ (I know of no other examples myself).
>
> which to me suggests that it's the behavior that was implemented in 5.2
that needed the _clear justification_.

Fair points, and thanks for the thoughtful reply.

My view is that Django settings are best reserved for configuration values
that affect the **behavior of the web service** itself (i.e. when running
in "real" deployments) not development-time conveniences. For those,
environment variables strike a better balance without expanding the
settings surface. It's somewhat like hiding warnings (which can be done
via an env var), but quite different from silencing system checks (which
is actually a setting) which are often tied to actual deployment readiness
and can impact whether a real server should run at all.

> oh well...this is probably not the hill that I'll die on

I appreciate you raising it, and I agree it's not a hill to die on.
--
Ticket URL: <https://code.djangoproject.com/ticket/36527#comment:4>

[Django]

#36527: Allow for runserver development server warning to be silenced via settings.
-------------------------------------+-------------------------------------
Reporter: Klaas van Schelven | Owner: (none)
Type: New feature | Status: closed
Component: Core (Management | Version: 5.2
commands) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Klaas van Schelven):

Thanks for ''your'' thoughtful reply.

>My view is that Django settings are best reserved for configuration

values that affect the behavior of the web service itself

I get that!
--
Ticket URL: <https://code.djangoproject.com/ticket/36527#comment:5>