mirror of https://github.com/python/cpython.git
Clarified warning about logging use from asynchronous signal handlers.
This commit is contained in:
parent
a178a69819
commit
353a85f99c
|
@ -2351,9 +2351,10 @@ needing to be done by its clients. It achieves this though using threading
|
||||||
locks; there is one lock to serialize access to the module's shared data, and
|
locks; there is one lock to serialize access to the module's shared data, and
|
||||||
each handler also creates a lock to serialize access to its underlying I/O.
|
each handler also creates a lock to serialize access to its underlying I/O.
|
||||||
|
|
||||||
Note that in Linux/Unix environments, threading APIs may not be usable in
|
If you are implementing asynchronous signal handlers using the :mod:`signal`
|
||||||
asynchronous signal handlers. This may mean that you cannot use logging from
|
module, you may not be able to use logging from within such handlers. This is
|
||||||
within asynchronous signal handlers; please check your OS documentation.
|
because lock implementations in the :mod:`threading` module are not always
|
||||||
|
re-entrant, and so cannot be invoked from such signal handlers.
|
||||||
|
|
||||||
Configuration
|
Configuration
|
||||||
-------------
|
-------------
|
||||||
|
|
Loading…
Reference in New Issue