innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Reworded a paragraph in the logging docs.

This commit is contained in:
Ramiro Morales 2013-09-16 17:49:46 -03:00
parent 1234225068
commit 9d12f68a53
1 changed files with 10 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/topics/logging.txt
View File

@ -211,14 +211,16 @@ handlers, filters and formatters that you want in your logging setup,
and the log levels and other properties that you want those components
to have.
Prior to Django 1.5, the :setting:`LOGGING` setting overwrote the :ref:`default
Django logging configuration <default-logging-configuration>`. From Django
1.5 forward, the project's logging configuration is merged with Django's
defaults, hence you can decide if you want to add to, or replace the existing
configuration. To completely override the default configuration, set the
``disable_existing_loggers`` key to ``True`` (which is the default) in the
:setting:`LOGGING` dictConfig. Alternatively you can redefine some or all of
the loggers by setting ``disable_existing_loggers`` to ``False``.
Prior to Django 1.5, the :setting:`LOGGING` setting always overwrote the
:ref:`default Django logging configuration <default-logging-configuration>`.
From Django 1.5 forward, it is possible to get the project's logging
configuration merged with Django's defaults, hence you can decide if you want to
add to, or replace the existing configuration.
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. Alternatively you can redefine some or all of the loggers by
setting ``disable_existing_loggers`` to ``False``.
Logging is configured as soon as settings have been loaded
(either manually using :func:`~django.conf.settings.configure` or when at least