New submission from himkt <hi...@klis.tsukuba.ac.jp>:
Currently documentation says we can check call_args_list by providing a list of
tuples of arguments.
```
>>> expected = [(), ((3, 4),), ({'key': 'fish', 'next': 'w00t!'},)]
>>> mock.call_args_list == expected
True
```
(from
https://docs.python.org/3.11/library/unittest.mock.html#unittest.mock.Mock.call_args_list)
However, I think we have to wrap all arguments with `call`.
I'd happy to send a patch if it should be fixed.
### Reproduce:
```
import time
from unittest.mock import call
from unittest.mock import patch
with patch("time.sleep") as mock_obj:
time.sleep(1)
time.sleep(2)
print("mock_obj.call_args_list")
print(mock_obj.call_args_list)
print("mock_obj.call_args_list == [(1,), (2,)]")
print(mock_obj.call_args_list == [(1,), (2,)])
print("mock_obj.call_args_list == [call(1,), call(2,)]")
print(mock_obj.call_args_list == [call(1,), call(2,)])
```
```
> python demo.py
>
> 2022-04-04 12:03:18
mock_obj.call_args_list
[call(1), call(2)]
mock_obj.call_args_list == [(1,), (2,)]
False
mock_obj.call_args_list == [call(1,), call(2,)]
True
```
### Links
- Documentation in repo:
https://github.com/python/cpython/blob/4216dce04b7d3f329beaaafc82a77c4ac6cf4d57/Doc/library/unittest.mock.rst
- Documentation in page:
https://docs.python.org/3.11/library/unittest.mock.html#unittest.mock.Mock.call_args_list
----------
assignee: docs@python
components: Documentation
messages: 416650
nosy: docs@python, himkt
priority: normal
severity: normal
status: open
title: Documentation for asserting values of `unittest.mock.Mock.call_args_list`
type: behavior
versions: Python 3.11
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue47209>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
