test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

More accurate terminology ("logger" instead of "logging handler") in logging documentation.

This commit is contained in:
Kal Sze 2019-04-18 10:58:13 +08:00 committed by Carlton Gibson
parent eb629f4c02
commit aa6c620249
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/topics/logging.txt
View File

@ -164,10 +164,9 @@ is a parent of the ``project.interesting`` logger.
Why is the hierarchy important? Well, because loggers can be set to Why is the hierarchy important? Well, because loggers can be set to
*propagate* their logging calls to their parents. In this way, you can *propagate* their logging calls to their parents. In this way, you can
define a single set of handlers at the root of a logger tree, and define a single set of handlers at the root of a logger tree, and
capture all logging calls in the subtree of loggers. A logging handler capture all logging calls in the subtree of loggers. A logger defined
defined in the ``project`` namespace will catch all logging messages in the ``project`` namespace will catch all logging messages issued on
issued on the ``project.interesting`` and the ``project.interesting`` and ``project.interesting.stuff`` loggers.
``project.interesting.stuff`` loggers.
This propagation can be controlled on a per-logger basis. If This propagation can be controlled on a per-logger basis. If
you don't want a particular logger to propagate to its parents, you you don't want a particular logger to propagate to its parents, you