Add minor clarification in logging documentation. (GH-22167)
This commit is contained in:
parent
640e8e1d5f
commit
76553e5d2e
|
@ -575,9 +575,9 @@ The useful mapping keys in a :class:`LogRecord` are given in the section on
|
|||
pickled and sent across the wire, but you should be careful if you have
|
||||
more than one :class:`Formatter` subclass which customizes the formatting
|
||||
of exception information. In this case, you will have to clear the cached
|
||||
value after a formatter has done its formatting, so that the next
|
||||
formatter to handle the event doesn't use the cached value but
|
||||
recalculates it afresh.
|
||||
value (by setting the *exc_text* attribute to ``None``) after a formatter
|
||||
has done its formatting, so that the next formatter to handle the event
|
||||
doesn't use the cached value, but recalculates it afresh.
|
||||
|
||||
If stack information is available, it's appended after the exception
|
||||
information, using :meth:`formatStack` to transform it if necessary.
|
||||
|
|
Loading…
Reference in New Issue