Issue #7851: logging: clarification on logging configuration files.
This commit is contained in:
parent
d840e5174d
commit
0e6e97d9ad
|
@ -422,6 +422,13 @@ You can see that the config file approach has a few advantages over the Python
|
||||||
code approach, mainly separation of configuration and code and the ability of
|
code approach, mainly separation of configuration and code and the ability of
|
||||||
noncoders to easily modify the logging properties.
|
noncoders to easily modify the logging properties.
|
||||||
|
|
||||||
|
Note that the class names referenced in config files need to be either relative
|
||||||
|
to the logging module, or absolute values which can be resolved using normal
|
||||||
|
import mechanisms. Thus, you could use either `handlers.WatchedFileHandler`
|
||||||
|
(relative to the logging module) or `mypackage.mymodule.MyHandler` (for a
|
||||||
|
class defined in package `mypackage` and module `mymodule`, where `mypackage`
|
||||||
|
is available on the Python import path).
|
||||||
|
|
||||||
.. _library-config:
|
.. _library-config:
|
||||||
|
|
||||||
Configuring Logging for a Library
|
Configuring Logging for a Library
|
||||||
|
|
|
@ -55,6 +55,8 @@ Core and Builtins
|
||||||
Library
|
Library
|
||||||
-------
|
-------
|
||||||
|
|
||||||
|
- Issue #7851: logging: clarification on logging configuration files.
|
||||||
|
|
||||||
- Issue #4772: Raise a ValueError when an unknown Bluetooth protocol is
|
- Issue #4772: Raise a ValueError when an unknown Bluetooth protocol is
|
||||||
specified, rather than fall through to AF_PACKET (in the `socket` module).
|
specified, rather than fall through to AF_PACKET (in the `socket` module).
|
||||||
Also, raise ValueError rather than TypeError when an unknown TIPC address
|
Also, raise ValueError rather than TypeError when an unknown TIPC address
|
||||||
|
|
Loading…
Reference in New Issue