@@ -695,15 +695,15 @@ noncoders to easily modify the logging properties.
695
695
.. warning :: The :func:`fileConfig` function takes a default parameter,
696
696
``disable_existing_loggers ``, which defaults to ``True `` for reasons of
697
697
backward compatibility. This may or may not be what you want, since it
698
- will cause any loggers existing before the :func: `fileConfig ` call to
699
- be disabled unless they (or an ancestor) are explicitly named in the
700
- configuration. Please refer to the reference documentation for more
698
+ will cause any non-root loggers existing before the :func: `fileConfig `
699
+ call to be disabled unless they (or an ancestor) are explicitly named in
700
+ the configuration. Please refer to the reference documentation for more
701
701
information, and specify ``False `` for this parameter if you wish.
702
702
703
703
The dictionary passed to :func: `dictConfig ` can also specify a Boolean
704
704
value with key ``disable_existing_loggers ``, which if not specified
705
705
explicitly in the dictionary also defaults to being interpreted as
706
- ``True ``. This leads to the logger-disabling behaviour described above,
706
+ ``True ``. This leads to the logger-disabling behaviour described above,
707
707
which may not be what you want - in which case, provide the key
708
708
explicitly with a value of ``False ``.
709
709
@@ -802,7 +802,7 @@ the best default behaviour.
802
802
If for some reason you *don't * want these messages printed in the absence of
803
803
any logging configuration, you can attach a do-nothing handler to the top-level
804
804
logger for your library. This avoids the message being printed, since a handler
805
- will be always be found for the library's events: it just doesn't produce any
805
+ will always be found for the library's events: it just doesn't produce any
806
806
output. If the library user configures logging for application use, presumably
807
807
that configuration will add some handlers, and if levels are suitably
808
808
configured then logging calls made in library code will send output to those
0 commit comments