You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would match the behaviour of the equivalent methods in mock
Currently, I can pass new_callable=AsyncMock to make it work, but then mypy type checking fails because the type hints state that the methods return MagicMock. The return type is a union in the mock stubs.
The text was updated successfully, but these errors were encountered:
This was a while ago now so I am doing some digging trying to remember. There is a chain of issues that leads to testing-cabal/mock#500 where I included a mypy error.
The repo this was happening is https://github.com/dls-controls/odinprocservcontrol. I have created a mypy branch from an old commit to recreate the problem here. It works on master with the updatedtypes-mock. If it is useful to recreate the problem locally, checkout the mypy branch and do a pipenv install --dev --ignore-pipfile and pipenv run mypy tests.
I have briefly looked through #364, but don't immediately understand the detail of the change - is this useful information? Let me know if there is anything else I can do to help.
This would match the behaviour of the equivalent methods in
mock
Currently, I can pass
new_callable=AsyncMock
to make it work, but then mypy type checking fails because the type hints state that the methods returnMagicMock
. The return type is a union in the mock stubs.The text was updated successfully, but these errors were encountered: