#25523: manage.py runserver ignores logging configuration error and shows wrong
exception
--------------------------------------------+--------------------
Reporter: coldmind | Owner: nobody
Type: Bug | Status: new
Component: Core (Management commands) | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------------+--------------------
While trying to `manage.py runserver`, when `LOGGING` contains some error
(e.g. log folder is missing, or `version` key is not included to logging
configuration dict), runserver internals is catching actual exception and
simply passing, and shows wrong error:
{{{
django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.
}}}
Here is a problem:
{{{
def setup():
"""
Configure the settings (this happens as a side effect of accessing the
first setting), configure logging and populate the app registry.
"""
...
configure_logging(settings.LOGGING_CONFIG, settings.LOGGING) # <-
exception from here is ignored
apps.populate(settings.INSTALLED_APPS) # <- this shows exception, but
should show exception about logging
}}}
Tested on master and 1.8.
1.7 works as expected
--
Ticket URL: <https://code.djangoproject.com/ticket/25523>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/051.8ac5357627706e8fd49fbe61ed260f06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
