-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
waitSignal swallows exceptions with raising=True #59
Comments
Fixed, thanks! 😄 The problem was on the |
That was an easier fix than I thought - thanks! 👍 What if an exception happens during |
Yes the problem was that it was overwriting the original exception. If Em sex, 12 de jun de 2015 01:36, Florian Bruhin notifications@github.com
|
Hi,
Do we have an idea of when we would like have a 2.8.0 release, or at least
what we would like to see in that new version?
And about 2.7.2? I see there are a couple of fixes that are in master but
should be backported to pytest-2.7 branch before making a 2.7.2 release.
Cheers,
|
It sounds like you're replying to the wrong mail - this is |
Oh dear. 😅 |
When
qtbot.waitSignal(..., raising=True)
is used and an exception in the with-block happens (which causes the signal to not be emitted), it's silently ignored andSignalTimeoutError
is raised instead.I don't really know what the best way to fix this would be (because of the existing Qt exception capturing), but I have a test case:
The text was updated successfully, but these errors were encountered: