#18518: wsgi.py does not overwrite DJANGO_SETTINGS_MODULE in apache prefork
-------------------------------+--------------------------------------
Reporter: schaefer@… | Owner: nobody
Type: Bug | Status: closed
Component: Uncategorized | Version: 1.4
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 carljm):
* status: new => closed
* needs_docs: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_better_patch: => 0
Comment:
There is a reason to try to avoid overwriting the environment variable -
there are quite a few use cases where you might want to set the
environment variable yourself externally, if you are using multiple
different settings files in your project (a common practice). The value
hardcoded in the wsgi file is intended only as a fallback default. In
general, hardcoded values should not override values set explicitly in the
environment.
Running multiple different Django sites in the same process under
preforked Apache is an edge case, and it's easy enough to change the
default wsgi file in your project (or use SetEnv in the virtualhost) if
you are in that situation.
--
Ticket URL: <https://code.djangoproject.com/ticket/18518#comment:1>
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 https://groups.google.com/groups/opt_out.
