#15064: DJANGO_SETTINGS_MODULE doesn't work with runserver
-------------------------------------+-------------------------------------
Reporter: olau | Owner: ShawnMilo
Type: Bug | Status: new
Milestone: | Component: Core (Management
Version: 1.3 | commands)
Resolution: | Severity: Normal
Triage Stage: Accepted | Keywords:
Needs documentation: 0 | Has patch: 1
Patch needs improvement: 1 | Needs tests: 0
| Easy pickings: 1
-------------------------------------+-------------------------------------
Comment (by ShawnMilo):
{{{
I had to add back the global_settings import that was just removed
yesterday because my test uses it.
The code patch is a simple one-line fix.
Brief description of the test, since it's more complicated:
There are three conditions that may exist when
django.core.management.setup_environ is called.
1. The optional kwarg original_settings_path is passed in (takes
precedence).
action: use original_settings_path
2. original_settings_path not passed, DJANGO_SETTINGS_MODULE in
environment.
action: use DJANGO_SETTINGS_MODULE (fixed by this patch)
3. original_settings_path not passed, DJANGO_SETTINGS_MODULE not
in environment.
action: use default (was happening for #2 before this patch)
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/15064#comment:13>
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 [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.
