Re: [Django] #14628: Document which settings can be changed at runtime

[Django]

#14628: Document which settings can be changed at runtime
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
NicoEchaniz | Status: new
Type: | Component: Documentation
Cleanup/optimization | Severity: Normal
Milestone: | Keywords: settings
Version: 1.2 | django.conf
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by Danny W. Adair <danny.adair@…>):

* cc: danny.adair@… (added)
* ui_ux: => 0
* easy: => 0

Comment:

I think that once it's documented which settings can be changed at
runtime, it would be nice to directly support such runtime changes, maybe
even in conjunction with the sites framework (speaking of "optional").

Having one central place for settings is great, and it would be good if
runtime changes would not necessitate using another app and therefore
different import - see also my question on SO
http://stackoverflow.com/questions/6528723/changing-django-settings-at-
runtime

--
Ticket URL: <https://code.djangoproject.com/ticket/14628#comment:10>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#14628: Document which settings can be changed at runtime
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
NicoEchaniz | Status: new
Type: | Component: Documentation
Cleanup/optimization | Severity: Normal
Milestone: | Keywords: settings
Version: 1.2 | django.conf
Resolution: | Has patch: 0
Triage Stage: Accepted | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------

Changes (by tomchristie):

* cc: tom@… (added)

--
Ticket URL: <https://code.djangoproject.com/ticket/14628#comment:11>

[Django]

#14628: Document which settings can be changed at runtime

--------------------------------------+------------------------------------
Reporter: NicoEchaniz | Owner: nobody
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: 1.2
Severity: Normal | Resolution: wontfix
Keywords: settings django.conf | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Carlton Gibson):

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

Comment:

So 10 years later, I'm going to close this as wontfix.
[https://docs.djangoproject.com/en/3.1/topics/settings/#altering-settings-
at-runtime The docs are clear that this isn't supported]:

> You shouldn’t alter settings in your applications at runtime.

Maybe it's possible, for some settings, but short of a patch actually
showing how we can document this safely and simply, this isn't a foot-gun
we should be in the market of enabling.

--
Ticket URL: <https://code.djangoproject.com/ticket/14628#comment:12>