mirror of https://github.com/python/cpython
Merged documentation update from 3.4.
This commit is contained in:
commit
33683dfb25
|
@ -1027,7 +1027,7 @@ You can write code like this::
|
||||||
so that if the logger's threshold is set above ``DEBUG``, the calls to
|
so that if the logger's threshold is set above ``DEBUG``, the calls to
|
||||||
:func:`expensive_func1` and :func:`expensive_func2` are never made.
|
: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
|
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
|
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
|
want to avoid calling a method in tight loops), you can cache the result of a
|
||||||
|
|
Loading…
Reference in New Issue