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 nose2? #18
Comments
Hi, thanks for the report, I can reproduce this and will look into it. |
Turns out this is not an issue in flexmock, in certain sense. If Twisted is installed, flexmock will try to hook up into
I'm not familiar with nose2 enough to be able to tell which of the following is true:
I'll try to learn more about nose2 vs twisted.trial to be able to tell which one of the above cases this is and then act on it - either by reporting issue for nose2 or twisted or trying to figure out how to fix this on flexmock's side. |
Interesting. It seems like not many people are using nose2. Not sure why |
So I switched to |
Thanks, so at least you have a workaround for now. In the meanwhile, I'll try to get some time to investigate this further :) |
Any update on this? Definitely seems like there are issues with
running this succeeds:
|
I think I see the issue. Nose2 has it's own TestResult class, to send events to plugins for stopTest, etc. So patching the unittest one makes no difference. It also lazy-loads and keeps TestCase instances around. I am thinking about writing a flexmock plugin for nose2, rather than adding another special case here. |
Hey, sorry for the late response here. I've been extremely busy both in work and personal life lately and didn't have any time to take care of flexmock. This should improve in the upcoming weeks, so I'll definitely get to this. Thanks for your patience. |
Running a simple test:
without Twisted, the test passes. With Twisted installed (no other changes), get:
The text was updated successfully, but these errors were encountered: