#14628: Document which settings can be changed at runtime
------------------------------------+---------------------------------------
Reporter: NicoEchaniz | Owner: nobody
Status: new | Milestone:
Component: Documentation | Version: 1.2
Resolution: | Keywords: settings django.conf
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------+---------------------------------------
Changes (by jacob):
* needs_better_patch: => 0
* summary: missing documentation about which settings can be safely
changed at runtime => Document which settings
can be changed at runtime
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'd like to put together a document that breaks settings down into three
categories:
* Things you can change at run-time (e.g. a middleware) without breaking
anything.
* Things you can change at run-time as long as you're careful and
trigger re-loading, clear a cache, or dance through some other hoop. It's
OK if this requires reading the source.
* Things you should absolutely never change at runtime.
This might also involve code fixes to ensure that settings can actually
fit into these categories.
--
Ticket URL: <http://code.djangoproject.com/ticket/14628#comment:1>
Django <http://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-upda...@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.
