Hi Elad,
Can you open an issue on https://bugs.python.org/ and post your findings there? I don't think it makes sense to continue discussing this on python-dev. (note that opening a bug doesn't mean it will be fixed quickly, but at least it's recorded somewhere instead of being lost in the mailing-list archives) Best regards Antoine. On Wed, 26 Feb 2020 18:47:39 -0000 "Elad Lahav" <e2la...@gmail.com> wrote: > I believe that the problem is in logging/__init__.py, which registers an > atfork() handler for re-initializing its lock. However, as part of this > process it attempts to acquire the module lock, which has not been > reinitialized and so still reflects the parent's state of the lock. > > --Elad _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/6RH32RIIACZZ3PLLASELUNNQCWYU23W4/ Code of Conduct: http://python.org/psf/codeofconduct/
