Manage.py loads the wrong settings file before it loads the right one
|Reported by:||Owned by:||nobody|
|Component:||Core (Management commands)||Version:||1.3|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
When you use manage.py runserver --settings=othersettings, it still imports the settings.py file, even though this is not the settings file you want to use. If this settings file raises an exception, manage.py will stop there. I don't think settings.py should be relevant when you override the settings setting.