Opened 15 years ago

Closed 14 years ago

#12786 closed (worksforme)

runserver --settings option does not work.

Reported by: ErikW Owned by: nobody
Component: django-admin.py runserver Version: 1.2-alpha
Severity: Keywords:
Cc: erik@… Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I just updated to the latest trunk r12384 and the settings option for the runserver management command doesn't seem to be working.

I have 2 sites configured:
settings.py (site 1)
settings_2.py (site 2)

# ./manage.py runserver --settings=settings_2
Validating models...
0 errors found

Django version 1.2 alpha 1 SVN-12385, using settings 'linx.settings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

I've added symlinked my django project directory directly into my site-packages -- so it is on the python path.

Change History (2)

comment:1 by Alex Gaynor, 15 years ago

Triage Stage: Unreviewed → Accepted

comment:2 by Joshua Ginsberg <jag@…>, 14 years ago

Resolution: → worksforme
Status: new → closed

I can't presently replicate this bug.

Pointy-Stick:djangodev jag$ PYTHONPATH=/Users/jag/devel/apps/django-trunk python manage.py runserver --settings=djangodev.othersettings
Validating models...
0 errors found

Django version 1.3 pre-alpha SVN-13405, using settings 'djangodev.othersettings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
^C
Pointy-Stick:djangodev jag$ PYTHONPATH=/Users/jag/devel/apps/django-trunk pyth manage.py runserver --settings=othersettings
Validating models...
0 errors found

Django version 1.3 pre-alpha SVN-13405, using settings 'othersettings'
Development server is running at http://127.0.0.1:8000/
Quit the server with CONTROL-C.

If I've missed something, please reopen. Thanks!

-jag

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