summaryrefslogtreecommitdiffstats
path: root/Doc
diff options
context:
space:
mode:
authorVinay Sajip <vinay_sajip@yahoo.co.uk>2010-02-04 20:23:45 (GMT)
committerVinay Sajip <vinay_sajip@yahoo.co.uk>2010-02-04 20:23:45 (GMT)
commit0e6e97d9adf276572fc409e993d0284871e13ab9 (patch)
tree6e014a7b7aa122c27b3904aa77eb7dbe41f8fed7 /Doc
parentd840e5174dc8d5407b56e377aa1e608ebe5cf535 (diff)
downloadcpython-0e6e97d9adf276572fc409e993d0284871e13ab9.zip
cpython-0e6e97d9adf276572fc409e993d0284871e13ab9.tar.gz
cpython-0e6e97d9adf276572fc409e993d0284871e13ab9.tar.bz2
Issue #7851: logging: clarification on logging configuration files.
Diffstat (limited to 'Doc')
-rw-r--r--Doc/library/logging.rst7
1 files changed, 7 insertions, 0 deletions
diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst
index 8a2443a..bca497f 100644
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -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
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:
Configuring Logging for a Library