Gregory P. Smith 19003841e9 bpo-6721: Hold logging locks across fork() (GH-4071) ... bpo-6721: When os.fork() was called while another thread holds a logging lock, the child process may deadlock when it tries to log. This fixes that by acquiring all logging locks before fork and releasing them afterwards. A regression test that fails before this change is included. Within the new unittest itself: There is a small _potential_ due to mixing of fork and a thread in the child process if the parent's thread happened to hold a non-reentrant library call lock (malloc?) when the os.fork() happens. buildbots and time will tell if this actually manifests itself in this test or not. :/ A functionality test that avoids that would be a challenge. An alternate test that isn't trying to produce the deadlock itself but just checking that the release and acquire calls are made would be the next best alternative if so.		2018-09-13 22:08:31 -07:00
..
__init__.py	bpo-6721: Hold logging locks across fork() (GH-4071)	2018-09-13 22:08:31 -07:00
config.py	bpo-33978: Close existing handlers before logging (re-)configuration. (GH-8008)	2018-07-02 09:57:46 +01:00
handlers.py	bpo-30904: Removed duplicated Host: header. (#4465)	2017-11-19 18:36:17 +00:00