summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLawouach <sh@defuze.org>2014-04-27 17:42:11 +0200
committerLawouach <sh@defuze.org>2014-04-27 17:42:11 +0200
commit0c2007ded1375aa784781c0cdca32645420fdbfe (patch)
tree5450a0e7508e1852348aa92ffd2ab7e56a8fad5d
parent627a56dc352306c32d4bb094e35de4ffa663ea10 (diff)
downloadcherrypy-0c2007ded1375aa784781c0cdca32645420fdbfe.tar.gz
actually no
-rw-r--r--sphinx/source/basics.rst12
1 files changed, 3 insertions, 9 deletions
diff --git a/sphinx/source/basics.rst b/sphinx/source/basics.rst
index d09da86b..ee3ae167 100644
--- a/sphinx/source/basics.rst
+++ b/sphinx/source/basics.rst
@@ -190,7 +190,9 @@ Play along with your other loggers
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Your application may aobviously already use the :mod:`logging`
-module to trace application level messages.
+module to trace application level messages. CherryPy will not
+interfere with them as long as your loggers are explicitely
+named. This would work nicely:
.. code-block:: python
@@ -201,14 +203,6 @@ module to trace application level messages.
stream.setLevel(logging.INFO)
logger.addHandler(stream)
-In order to avoid the CherryPy loggers to pick up messaging,
-it is a good idea to execute the two following line:
-
-.. code-block:: python
-
- cherrypy.log.error_log.propagate = False
-
-
.. _config:
Configuring