Opened 8 years ago

Last modified 8 years ago

#27522 closed Bug

./manage runserver --nostatic doesn't return a traceback — at Initial Version

Reported by: Jeroen van Veen Owned by: nobody
Component: Core (Management commands) Version: dev
Severity: Normal Keywords: runserver nostatic
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

When running ./manage runserver --nostatic, I expect a traceback to be returned when
a syntax error occurs, and I expect the autoreloader still to be available. Instead, the
runserver command exits like:

usage: manage.py runserver [-h] [--version] [-v {0,1,2,3}]

[--settings SETTINGS] [--pythonpath PYTHONPATH]
[--traceback] [--no-color] [--ipv6] [--nothreading]
[--noreload]
[addrport]

manage.py runserver: error: unrecognized arguments: --nostatic

Change History (0)

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