Lines Matching full:loggers

40 * Loggers expose the interface that application code directly uses.
41 * Handlers send the log records (created by loggers) to the appropriate
53 Loggers have the following attributes and methods.  Note that Loggers should
60 Loggers that are further down in the hierarchical list are children of loggers
62 loggers with names of ``foo.bar``, ``foo.bar.baz``, and ``foo.bam`` are all
64 package hierarchy, and identical to it if you organise your loggers on a
75       passed to the handlers of higher level (ancestor) loggers, in addition to
77       ancestor loggers' handlers - neither the level nor filters of the ancestor
78       loggers in question are considered.
81       of ancestor loggers.
86       level and filter settings] be passed in turn to any handlers attached to loggers
98          hierarchy, then it will see all events logged by all descendant loggers,
116       NOTSET, its chain of ancestor loggers is traversed until either an ancestor with
363       Loggers can now be pickled and unpickled.
648 ``Filters`` can be used by ``Handlers`` and ``Loggers`` for more sophisticated
651 initialized with 'A.B' will allow events logged by loggers 'A.B', 'A.B.C',
670 emitted by the handler, whereas filters attached to loggers are consulted
673 been generated by descendant loggers will not be filtered by a logger's filter
674 setting, unless the filter has also been applied to those descendant loggers.
1095    Provides an overriding level *level* for all loggers which takes precedence over
1104    levels of individual loggers.
1285    function is typically called before any loggers are instantiated by applications
1287    time, do not instantiate loggers directly using the subclass: continue to use
1288    the :func:`logging.getLogger` API to get your loggers.