id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
24361	The doc is not right w.r.t. LOGGING overwriting.	Vlada Macek	nobody	"The https://github.com/django/django/blob/master/docs/topics/logging.txt says

    If the `disable_existing_loggers` key in the :setting:`LOGGING` dictConfig is set to `True` (which is the default) the default configuration is completely overridden.

That is **not right** and it is pretty painful to trace down that the `django.request` and `django.security`, although disabled, don't propagate to the root logger even when `disable_existing_loggers` in my LOGGING is `True`. One would expect the disabling would allow the logger to propagate again.

Many people apparently already ran into this.

There are Stack Overflow questions and blog posts about this topic. Best of them I found is here: http://www.caktusgroup.com/blog/2015/01/27/Django-Logging-Configuration-logging_config-default-settings-logger/

It suggests the working way to put to `settings` to **really erase the default logging**. I think it should definitely be stated in the doc.

{{{
LOGGING_CONFIG = None
LOGGING = {...}  # whatever you want

import logging.config
logging.config.dictConfig(LOGGING)
}}}

The logging system is complex by itself, something it is not a pleasure to work with for many. The reset path eliminating the confusion would be most welcome.
"	Bug	closed	Documentation	dev	Normal	fixed			Accepted	1	0	0	0	0	0