Lines Matching full:loggers

48 * Loggers expose the interface that application code directly uses.
49 * Handlers send the log records (created by loggers) to the appropriate
61 Loggers have the following attributes and methods.  Note that Loggers should
68 Loggers that are further down in the hierarchical list are children of loggers
70 loggers with names of ``foo.bar``, ``foo.bar.baz``, and ``foo.bam`` are all
72 package hierarchy, and identical to it if you organise your loggers on a
83       passed to the handlers of higher level (ancestor) loggers, in addition to
85       ancestor loggers' handlers - neither the level nor filters of the ancestor
86       loggers in question are considered.
89       of ancestor loggers.
94       level and filter settings] be passed in turn to any handlers attached to loggers
106          hierarchy, then it will see all events logged by all descendant loggers,
124       NOTSET, its chain of ancestor loggers is traversed until either an ancestor with
375       Loggers can now be pickled and unpickled.
705 ``Filters`` can be used by ``Handlers`` and ``Loggers`` for more sophisticated
708 initialized with 'A.B' will allow events logged by loggers 'A.B', 'A.B.C',
727 emitted by the handler, whereas filters attached to loggers are consulted
730 been generated by descendant loggers will not be filtered by a logger's filter
731 setting, unless the filter has also been applied to those descendant loggers.
1170    Provides an overriding level *level* for all loggers which takes precedence over
1179    levels of individual loggers.
1368    function is typically called before any loggers are instantiated by applications
1370    time, do not instantiate loggers directly using the subclass: continue to use
1371    the :func:`logging.getLogger` API to get your loggers.