Settings module passed through the command line (using --settings) is being ignored
|Reported by:||Owned by:||Adrian Holovaty|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Consider the following command:
[django_project_dir]/> python manage.py test --settings=custom_settings
custom_settings is present in the same directory as settings.py. However the settings present in custom_settings are ignored. It seems that changeset 6047 introduced changes wherein settings get configured *before* custom settings are activated.