Clarification on arbitrary object graph changes.

This commit is contained in:
Vinay Sajip 2009-10-28 10:19:38 +00:00
parent af00560910
commit e5d36b5814
1 changed files with 4 additions and 1 deletions

View File

@ -553,7 +553,10 @@ Furthermore, there is not a compelling case for arbitrarily altering
the object graph of loggers, handlers, filters, formatters at the object graph of loggers, handlers, filters, formatters at
run-time, once a configuration is set up; the verbosity of loggers and run-time, once a configuration is set up; the verbosity of loggers and
handlers can be controlled just by setting levels (and, in the case of handlers can be controlled just by setting levels (and, in the case of
loggers, propagation flags). loggers, propagation flags). Changing the object graph arbitrarily in
a safe way is problematic in a multi-threaded environment; while not
impossible, the benefits are not worth the complexity it adds to the
implementation.
Thus, when the ``incremental`` key of a configuration dict is present Thus, when the ``incremental`` key of a configuration dict is present
and is ``True``, the system will ignore any ``formatters`` and and is ``True``, the system will ignore any ``formatters`` and