[issue33667] Mock calls on mutable objects

Change by R. David Murray : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> Python unittest.mock.mock_calls stores references to arguments instead of their values ___ Python tracker

[issue33667] Mock calls on mutable objects

Pawel added the comment: Ok, fair enough. Thank You for explanation. I was just surprised with this behaviour. On the other hand, I don't like mutable objects and I'm trying to avoid them. -- ___ Python tracker

[issue33667] Mock calls on mutable objects

Lady Red added the comment: To have the behavior that you are expecting, I believe the mock would have to store a deep copy of every mutable object that is passed in to any of it's calls, in case that object later mutates. That would really expand the memory and time footprint of working wit

[issue33667] Mock calls on mutable objects

New submission from Pawel : When method of mocked object is called multiple times with mutable object as parameter and attribute of this object has been updated between calls, mock_calls is only aware of the last value. I think it unexpected behaviour, that mock doesn't track value changes. I'