mirror of https://github.com/python/cpython.git
gh-92859: Doc: add info about logging.debug() calling basicConfig() (GH-93063) (GH-93151)
(cherry picked from commit 2176898308
)
This commit is contained in:
parent
f0950585a3
commit
cea65730a7
|
@ -178,10 +178,11 @@ following example::
|
||||||
raise ValueError('Invalid log level: %s' % loglevel)
|
raise ValueError('Invalid log level: %s' % loglevel)
|
||||||
logging.basicConfig(level=numeric_level, ...)
|
logging.basicConfig(level=numeric_level, ...)
|
||||||
|
|
||||||
The call to :func:`basicConfig` should come *before* any calls to :func:`debug`,
|
The call to :func:`basicConfig` should come *before* any calls to
|
||||||
:func:`info` etc. As it's intended as a one-off simple configuration facility,
|
:func:`debug`, :func:`info`, etc. Otherwise, those functions will call
|
||||||
only the first call will actually do anything: subsequent calls are effectively
|
:func:`basicConfig` for you with the default options. As it's intended as a
|
||||||
no-ops.
|
one-off simple configuration facility, only the first call will actually do
|
||||||
|
anything: subsequent calls are effectively no-ops.
|
||||||
|
|
||||||
If you run the above script several times, the messages from successive runs
|
If you run the above script several times, the messages from successive runs
|
||||||
are appended to the file *example.log*. If you want each run to start afresh,
|
are appended to the file *example.log*. If you want each run to start afresh,
|
||||||
|
|
|
@ -242,6 +242,10 @@ is the module's name in the Python package namespace.
|
||||||
above example). In such circumstances, it is likely that specialized
|
above example). In such circumstances, it is likely that specialized
|
||||||
:class:`Formatter`\ s would be used with particular :class:`Handler`\ s.
|
:class:`Formatter`\ s would be used with particular :class:`Handler`\ s.
|
||||||
|
|
||||||
|
If no handler is attached to this logger (or any of its ancestors,
|
||||||
|
taking into account the relevant :attr:`Logger.propagate` attributes),
|
||||||
|
the message will be sent to the handler set on :attr:`lastResort`.
|
||||||
|
|
||||||
.. versionchanged:: 3.2
|
.. versionchanged:: 3.2
|
||||||
The *stack_info* parameter was added.
|
The *stack_info* parameter was added.
|
||||||
|
|
||||||
|
@ -1038,6 +1042,10 @@ functions.
|
||||||
above example). In such circumstances, it is likely that specialized
|
above example). In such circumstances, it is likely that specialized
|
||||||
:class:`Formatter`\ s would be used with particular :class:`Handler`\ s.
|
:class:`Formatter`\ s would be used with particular :class:`Handler`\ s.
|
||||||
|
|
||||||
|
This function (as well as :func:`info`, :func:`warning`, :func:`error` and
|
||||||
|
:func:`critical`) will call :func:`basicConfig` if the root logger doesn't
|
||||||
|
have any handler attached.
|
||||||
|
|
||||||
.. versionchanged:: 3.2
|
.. versionchanged:: 3.2
|
||||||
The *stack_info* parameter was added.
|
The *stack_info* parameter was added.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue