Context Navigation

Changes between Version 1 and Version 2 of Ticket #32915, comment 23

v1	v2
7	7	The user-facing problem is more significant than just the missing traceback on runserver. Because `settings.configured` stays `False`, `get_commands()` returns only the django.core commands and every other command defined by an app in `INSTALLED_APPS` silently disappears. The user runs `./manage.py actual_custom_command`, gets "Unknown command: 'actual_custom_command'", and is told nothing about why. Since we haven't shown the user the real error with their settings, they're getting mislead about the simplest way to fix the issue.
8	8
9		This ticket is focused on that same user problem: after a settings failure, `django.contrib.staticfiles` is silently not added to `INSTALLED_APPS`, so the `--nostatic` option disappears (since `runserver` is never overridden). The best solution isn't to patch `--nostatic` into the core command, it's to confront the user with the settings failure; once they fix that, `INSTALLED_APPS` and custom commands will work again.
	9	This ticket is focused on an instance of that same user problem: after a settings failure, `django.contrib.staticfiles` is silently not added to `INSTALLED_APPS`, so the `--nostatic` option disappears (since `runserver` is never overridden). The best solution isn't to patch `--nostatic` into the core command, it's to confront the user with the settings failure; once they fix that, `INSTALLED_APPS` and custom commands will work again.