Message345358
| Author | jcline |
|---|---|
| Recipients | jcline |
| Date | 2019-06-12.14:00:18 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1560348018.57.0.546920052201.issue37251@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
This is related to the new AsyncMock[0] class in Python 3.8b1. A simple reproducer is:
from unittest import mock
mock_obj = mock.MagicMock()
mock_obj.mock_func = mock.MagicMock(spec=lambda x: x)
with mock.patch.object(mock_obj, "mock_func") as nested:
print(type(nested))
Instead of a MagicMock (the behavior in Python 3.7) in Python 3.8b1 this results in an AsyncMock.
[0]https://github.com/python/cpython/pull/9296 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-06-12 14:00:18 | jcline | set | recipients: + jcline |
| 2019-06-12 14:00:18 | jcline | set | messageid: <1560348018.57.0.546920052201.issue37251@roundup.psfhosted.org> |
| 2019-06-12 14:00:18 | jcline | link | issue37251 messages |
| 2019-06-12 14:00:18 | jcline | create | |