-
Notifications
You must be signed in to change notification settings - Fork 105
Error when inspecting the signature of AsyncMock() #504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This package is a rolling backport of Please can you try and reproduce the problem on the latest release of Python 3, including alphas, and replace any import from If the issue still occurs, then please report upstream through https://github.com/python/cpython/issues as it will need to be fixed there so that it can be backported here and released to you. If not, reply with what you find out and we can re-open this issue. |
CPython issue : python/cpython#96127 |
@tirkarthi - I wonder if python/cpython#84753 ends up being a problem here? I remember the commit having changes to both |
@cjw296 I guess python/cpython#84753 is more of an issue with |
Yep, agreed, this is an upstread issue, so let's track on python/cpython#96127 |
Release 5.0.1 will hopefully fix this... |
What versions are you using?
What happened?
Upgrading from
mock==4.0.3
tomock==5.0.0
introduced an error while inspecting the signature of anAsyncMock()
coroutine function. I noticed someAsyncMock()
-related changes in the changelog, so I'm not sure whether this is the desired behavior, butAsyncMock()
docs state that this should return a coroutine-function-like object which should be inspectable.mock==4.0.3
:mock==5.0.0
:Thank you for your time :-)
The text was updated successfully, but these errors were encountered: