[issue41954] [mock] Recursion on mocking inspect.isfunction

Stanislav Levin added the comment: I see, thank you for your time. -- resolution: -> wont fix stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue41954] [mock] Recursion on mocking inspect.isfunction

Lisa Roach added the comment: Oof yeah, sorry my commit broke this but it is pretty hard to avoid. Mario is right in that it would be messy and challenging to ensure anything mocked from the stdlib doesn't also break mock itself. I want to mark this as `wont fix`, unless there is a compell

[issue41954] [mock] Recursion on mocking inspect.isfunction

Mario Corchero added the comment: Oh, well spotted. We could add some guards around the code in mock to still work when key stdlib functionality is mocked out, but this might make the mock code quite messy. Specially as we will have to make sure that not only the function we call are safe to

[issue41954] [mock] Recursion on mocking inspect.isfunction

Change by Karthikeyan Singaravelan : -- nosy: +cjw296, lisroach, mariocj89, michael.foord, xtreak ___ Python tracker ___ ___ Python-

[issue41954] [mock] Recursion on mocking inspect.isfunction

New submission from Stanislav Levin : With Python 3.8 the mocking of `inspect.isfunction` results in recursion. Please, consider a code snippet: ```python from unittest import TestCase from unittest.mock import patch import inspect class TestClass(TestCase): def setUp(self): patc