Opened 13 years ago

Closed 13 years ago

#17420 closed Bug (fixed)

Manage.py loads the wrong settings file before it loads the right one

Reported by: nickretallack@… Owned by: nobody
Component: Core (Management commands) Version: 1.3
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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.

Change History (1)

comment:1 by Aymeric Augustin, 13 years ago

Resolution: fixed
Status: newclosed

I think this was fixed by r16964. Please reopen the ticket if you can reproduce it on trunk.

Note: See TracTickets for help on using tickets.
Back to Top