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
conflict with asynctest project #124
Comments
I tried to debug this case and found that it seems that ['args', 'kwargs', 'self', 'spec'] but after: ['_spec_coroutines', 'args', 'kwargs', 'self', 'spec'] what is completely different from what we have here without ['__bool__', '__class__', '__delattr__', '__dir__', '__doc__', '__eq__', '__format__', '__ge__', '__getattribute__', '__gt__', '__hash__', '__init__', '__le__', '__lt__', '__ne__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__'] |
Thanks for analyzing the issue! Thanks 🍻 |
@hyzhak I tried to reproduce your issue with the code you provided but it didn't work out because of the mocking where I'm missing the And please update to sure version Thanks 🍰 |
I have some time now to tackle this issue. I've contacted Martin (maintainer of asynctest) - maybe there is a chance we can look at this together. In the meanwhile you'd be able to disable the monkey patching by setting the |
Fix patched built-in dir() method. Closes #124
I've just fixed it with #128 . Have fun and thanks for the report 🍻 |
Issue Type
It is Bug Report about conflict Sure lib and asynctest (https://github.com/Martiusweb/asynctest).
Versions & Configuration
Using:
sure=1.3.0
asynctest==0.7.1
Docker Python 3.5.1 (https://hub.docker.com/_/python/)
Steps to reproduce
I'm trying to use sure and asynctest in one test:
and it fails with error:
and if I will remove
import sure
we won't get error.After little bit investigation I've found that maybe problem that
Sure
mock somehow__dict__
. And seems is related to this caveat https://github.com/gabrielfalcao/sure/blob/master/docs/source/api-reference.rst#holy-guacamole-how-did-you-implement-that-feature-PS:
related issue in asynctest project Martiusweb/asynctest#18
The text was updated successfully, but these errors were encountered: