#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
-------------------------------+--------------------------------------
Comment (by Graham.Dumpleton@…):
You cannot use SetEnv to do anything. That does not affect process wide
environment variables when using mod_wsgi, only per request WSGI environ
which Django doesn't as far as I know pay attention to for this because it
is still stuck with this global variable to define what the settings are.
The root trigger for this problem has been documented in mod_wsgi
documentation for years:
http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Application_Environment_Variables
Use of multiple sub interpreters is not an edge case, it is actually the
default use case in mod_wsgi in that for every distinct WSGIScriptAlias,
each runs in a separate sub interpreter of the same process unless you
deliberately work out how to use daemon mode and force each WSGI
application into a separate daemon process group. Because the majority of
people don't read documentation, they don't usually use daemon mode and so
will be hit with this problem as soon as they try and host two Django
applications.
--
Ticket URL: <https://code.djangoproject.com/ticket/18518#comment:2>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
