From: Duane Griffin Date: Thu, 26 Jun 2025 14:18:32 +0000 (+1200) Subject: gh-91555: add warning to docs about possibility of deadlock/infinite recursion (GH... X-Git-Tag: v3.15.0a1~1172 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a4625d597f9fc2d083fbb9c22d3ffcec73b2061a;p=thirdparty%2FPython%2Fcpython.git gh-91555: add warning to docs about possibility of deadlock/infinite recursion (GH-135954) * gh-91555: add warning to docs about possibility of deadlock/infinite recursion Attempt to clarify in the documentation that care must be taken when using multiprocessing classes to implement logging since they have builtin internal logging, and hence may cause deadlock/infinite recursion. * Update Doc/library/logging.handlers.rst Co-authored-by: Vinay Sajip * Change whitespace. --------- Co-authored-by: Vinay Sajip --- diff --git a/Doc/library/logging.handlers.rst b/Doc/library/logging.handlers.rst index 8f3aa1dfdd0c..d74ef73ee284 100644 --- a/Doc/library/logging.handlers.rst +++ b/Doc/library/logging.handlers.rst @@ -1059,6 +1059,15 @@ possible, while any potentially slow operations (such as sending an email via .. note:: If you are using :mod:`multiprocessing`, you should avoid using :class:`~queue.SimpleQueue` and instead use :class:`multiprocessing.Queue`. + .. warning:: + + The :mod:`multiprocessing` module uses an internal logger created and + accessed via :meth:`~multiprocessing.get_logger`. + :class:`multiprocessing.Queue` will log ``DEBUG`` level messages upon + items being queued. If those log messages are processed by a + :class:`QueueHandler` using the same :class:`multiprocessing.Queue` instance, + it will cause a deadlock or infinite recursion. + .. method:: emit(record) Enqueues the result of preparing the LogRecord. Should an exception