-
-
Notifications
You must be signed in to change notification settings - Fork 231
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
twisted: don't encapsulate failures twice #145
Conversation
Codecov Report
@@ Coverage Diff @@
## master #145 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 13 13
Lines 791 791
Branches 101 101
=====================================
Hits 791 791
Continue to review full report at Codecov.
|
So yeah looks fair enough, however I think we have to add a tox env for Twisted with the old behavior to ensure we don’t break anything? It should be enough if it runs just the twisted parts of the test suite. |
Do you want me to do it? |
Yeah it would be nice if it were part of this PR. Also please remember to adapt .travis.yml. |
Done. Error seems unrelated to this PR. |
Thanks, could you add a changelog entry too, please? |
If a failure is already a Failure instance, don't encapsulate it into a Failure. Keep it as is. Fix hynek#144
In versions < 17, Failure is not a subclass of BaseException, while it is in versions > 17.
b2c0fc9
to
c4e3ecd
Compare
I have modified the first commit to add a changelog entry. |
Thanks! |
If a failure is already a Failure instance, don't encapsulate it into
a Failure. Keep it as is.
Fix #144
Note that I have no clue if this is actually correct. This fixes the failing test and it doesn't seem dumb to do that. I didn't investigate what changes triggered this problem. Maybe
Failure
was not aBaseException
in the past.