mirror of
https://github.com/python/cpython.git
synced 2025-11-01 02:38:53 +00:00
Issue #16884: Merged logging documentation fixes from 3.2.
This commit is contained in:
commit
0e82fd1f78
2 changed files with 37 additions and 21 deletions
|
|
@ -780,13 +780,14 @@ should have the desired effect. If an organisation produces a number of
|
|||
libraries, then the logger name specified can be 'orgname.foo' rather than
|
||||
just 'foo'.
|
||||
|
||||
**PLEASE NOTE:** It is strongly advised that you *do not add any handlers other
|
||||
than* :class:`~logging.NullHandler` *to your library's loggers*. This is
|
||||
because the configuration of handlers is the prerogative of the application
|
||||
developer who uses your library. The application developer knows their target
|
||||
audience and what handlers are most appropriate for their application: if you
|
||||
add handlers 'under the hood', you might well interfere with their ability to
|
||||
carry out unit tests and deliver logs which suit their requirements.
|
||||
.. note:: It is strongly advised that you *do not add any handlers other
|
||||
than* :class:`~logging.NullHandler` *to your library's loggers*. This is
|
||||
because the configuration of handlers is the prerogative of the application
|
||||
developer who uses your library. The application developer knows their
|
||||
target audience and what handlers are most appropriate for their
|
||||
application: if you add handlers 'under the hood', you might well interfere
|
||||
with their ability to carry out unit tests and deliver logs which suit their
|
||||
requirements.
|
||||
|
||||
|
||||
Logging Levels
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue