diff options
author | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2014-06-25 07:30:46 +0100 |
---|---|---|
committer | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2014-06-25 07:30:46 +0100 |
commit | ab960f838c71bcdedddf26de48c5c911051e8ada (patch) | |
tree | c55ac3e21e53a1bb20d2a9da20ff3837c25322b7 | |
parent | 97d3555029b02fa4b432c1a1259b64aaa31e4e3e (diff) | |
download | cpython-git-ab960f838c71bcdedddf26de48c5c911051e8ada.tar.gz |
Fixed typo in documentation.
-rw-r--r-- | Doc/howto/logging.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/howto/logging.rst b/Doc/howto/logging.rst index 0387bea4e1..4ce14f98ad 100644 --- a/Doc/howto/logging.rst +++ b/Doc/howto/logging.rst @@ -1027,7 +1027,7 @@ You can write code like this:: so that if the logger's threshold is set above ``DEBUG``, the calls to :func:`expensive_func1` and :func:`expensive_func2` are never made. -.. note:: In some cases, :meth:`~Logger.isEnabledFor` can iself be more +.. note:: In some cases, :meth:`~Logger.isEnabledFor` can itself be more expensive than you'd like (e.g. for deeply nested loggers where an explicit level is only set high up in the logger hierarchy). In such cases (or if you want to avoid calling a method in tight loops), you can cache the result of a |