[issue41768] unittest.mock spec calls class properties

Change by Alex Waygood : -- nosy: +lukasz.langa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41768] unittest.mock spec calls class properties

Nikita Sobolev added the comment: Related PR: https://github.com/python/cpython/pull/29901 -- nosy: +sobolevn ___ Python tracker ___

[issue41768] unittest.mock spec calls class properties

Change by Karthikeyan Singaravelan : -- nosy: +cjw296, lisroach, mariocj89 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue41768] unittest.mock spec calls class properties

Terry J. Reedy added the comment: Without lines numbers, I cannot test which of the two identical asserts failed. Either comments or msg arguments will differentiate. Nor can I run snippets from two different files. Here is a minimal reproducible self-contained code that demonstrates the

[issue41768] unittest.mock spec calls class properties

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[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 ___

[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