Issue 33309: Unittest Mock objects do not freeze arguments they are called with (original) (raw)

Issue33309

Created on 2018-04-18 15:53 by slacknate, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (3)
msg315456 - (view)	Author: Nate Duarte (slacknate) *	Date: 2018-04-18 15:53
It is possible to make a call with a Mock object, for example, where a dictionary is passed to the mock and later modified. If a call assertion is then made against the mock using the initial value/contents of the dictionary the assertion will fail.
msg319816 - (view)	Author: Karthikeyan Singaravelan (xtreak) *	Date: 2018-06-17 14:17
Thanks for the issue. I think this is documented here : https://docs.python.org/3/library/unittest.mock-examples.html#coping-with-mutable-arguments Thanks
msg326253 - (view)	Author: Karthikeyan Singaravelan (xtreak) *	Date: 2018-09-24 15:38
Thanks for the details. As part of triaging I am closing this as not a bug since passing mutable arguments to a mock object and modifying it is a documented behavior at https://docs.python.org/3/library/unittest.mock-examples.html#coping-with-mutable-arguments . Feel free to reopen this if needed. Thanks