From 03cd3d137e2c29484b020b9768a4741f1096be97 Mon Sep 17 00:00:00 2001 From: swatantra Date: Mon, 10 Jun 2019 00:58:30 +0530 Subject: [PATCH] Fixed #30553 -- Clarified the default value of disable_existing_loggers. --- docs/topics/logging.txt | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/docs/topics/logging.txt b/docs/topics/logging.txt index d1aa8a3ea9b..0820451709a 100644 --- a/docs/topics/logging.txt +++ b/docs/topics/logging.txt @@ -218,15 +218,15 @@ default logging configuration ` using the following scheme. If the ``disable_existing_loggers`` key in the :setting:`LOGGING` dictConfig is -set to ``True`` (which is the default) then all loggers from the default -configuration will be disabled. Disabled loggers are not the same as removed; -the logger will still exist, but will silently discard anything logged to it, -not even propagating entries to a parent logger. Thus you should be very -careful using ``'disable_existing_loggers': True``; it's probably not what you -want. Instead, you can set ``disable_existing_loggers`` to ``False`` and -redefine some or all of the default loggers; or you can set -:setting:`LOGGING_CONFIG` to ``None`` and :ref:`handle logging config yourself -`. +set to ``True`` (which is the ``dictConfig`` default if the key is missing) +then all loggers from the default configuration will be disabled. Disabled +loggers are not the same as removed; the logger will still exist, but will +silently discard anything logged to it, not even propagating entries to a +parent logger. Thus you should be very careful using +``'disable_existing_loggers': True``; it's probably not what you want. Instead, +you can set ``disable_existing_loggers`` to ``False`` and redefine some or all +of the default loggers; or you can set :setting:`LOGGING_CONFIG` to ``None`` +and :ref:`handle logging config yourself `. Logging is configured as part of the general Django ``setup()`` function. Therefore, you can be certain that loggers are always ready for use in your