#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.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
