[issue40091] Crash in logging._after_at_fork_child_reinit_locks()

melwitt added the comment: Hi, I've been following the work related to: https://bugs.python.org/issue6721 https://bugs.python.org/issue40089 because I encountered a problem where a standard library lock was held by a parent process at the time that child processes were forked, so the

[issue40091] Crash in logging._after_at_fork_child_reinit_locks()

melwitt added the comment: Thank you for explaining those details and pointing me in the right direction about the proper way to solve the problem in oslo.db. We still have to support python 3.6, so for now we will still need to do something different (in nova) to handle this (clear our

[issue41768] unittest.mock spec calls class properties

New submission from melwitt : When async magic method support was added to unittest.mock.Mock to address issue #26467, it introduced a getattr call [1] that causes class properties to be called when the class is used as a mock spec. This caused a problem for a test in my project when running

[issue41768] unittest.mock spec calls class properties

Change by melwitt : -- keywords: +patch pull_requests: +21264 stage: -> patch review pull_request: https://github.com/python/cpython/pull/22209 ___ Python tracker <https://bugs.python.org/issu