> This bug has actually been brought up before as an issue in the mock library repo [2] and is likely a bug in mock.
Correction: this does not seem to be a bug in mock -- same thing is happening in the python3.8 version of unittest.mock.
Back to the drawing board.
> This bug has actually been brought up before as an issue in the mock library repo [2] and is likely a bug in mock.
Correction: this does not seem to be a bug in mock -- same thing is happening in the python3.8 version of unittest.mock.
Back to the drawing board.