Opened 5 years ago

Closed 5 years ago

#25285 closed Cleanup/optimization (fixed)

Unknown django-admin command raises "settings not configured" when no project exists

Reported by: Maxime Lorant Owned by: nobody
Component: Core (Management commands) Version: master
Severity: Normal Keywords: django-admin command
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


When you try to execute a command that does not exist outside a Django project (e.g. createproject instead of startproject...), Django raise a ImproperlyConfigured that does not fit with the real error:

(testdjango):~/testdjango$ not-a-real-command test
Traceback (most recent call last):
  File "/root/testdjango/bin/", line 5, in <module>
  File "/root/testdjango/local/lib/python2.7/site-packages/django/core/management/", line 338, in execute_from_command_line
  File "/root/testdjango/local/lib/python2.7/site-packages/django/core/management/", line 330, in execute
  File "/root/testdjango/local/lib/python2.7/site-packages/django/core/management/", line 182, in fetch_command
  File "/root/testdjango/local/lib/python2.7/site-packages/django/conf/", line 48, in __getattr__
  File "/root/testdjango/local/lib/python2.7/site-packages/django/conf/", line 42, in _setup
django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.

The expected output is:

(testdjango):~/testdjango$ not-a-real-command test
Unknown command: 'not-a-real-command'
Type ' help' for usage.

Attachments (1)

unknown-command-exception.patch (695 bytes) - added by Maxime Lorant 5 years ago.
Suggestion of patch

Download all attachments as: .zip

Change History (6)

Changed 5 years ago by Maxime Lorant

Suggestion of patch

comment:1 Changed 5 years ago by Tim Graham

Easy pickings: unset
Summary: Unknown command raise the wrong exception when no project existUnknown django-admin command raises "settings not configured" when no project exists
Triage Stage: UnreviewedAccepted

I think your proposal makes sense. It keeps the fix for #21634, but only when using Claude, what do you think?

comment:2 Changed 5 years ago by Claude Paroz

comment:3 Changed 5 years ago by Maxime Lorant

Indeed, as a Django user, I would also prefer this implementation: it provides the correct error message and give a hint in case the user tried to use a custom command. (Also, it avoids hardcoded filename, like "django-admin" in the code...)

Thanks Claude.

comment:4 Changed 5 years ago by Tim Graham

Triage Stage: AcceptedReady for checkin

comment:5 Changed 5 years ago by Claude Paroz <claude@…>

Resolution: fixed
Status: newclosed

In c1893e2:

Fixed #25285 -- Provided unknown command message with plain

Thanks Maxime Lorant for the report and Tim Graham for suggesting
the improved comment.

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