-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Fix "except:" statements #14028
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
comment:4
Its pretty much a no-brainer. Ready for review? |
comment:5
Replying to @vbraun:
Not sure. The following is fairly reproducible when interrupting GAP:
The backtrace at this point (thanks to #14029) is attached. |
Attachment: sage_crash_IAI1or.log |
comment:6
The problem was removing the statement
New patch attached which should fix this. I also changed a few more instances of
to
in cases where the except-clause was doing cleanup + re-raise. |
Attachment: 14028_bare_except.patch.gz |
comment:7
Passes all long doctests, so ready for review. |
Reviewer: Volker Braun |
comment:8
Looks good to me. |
Merged: sage-5.7.beta2 |
Replace
by
(or an other exception where it makes sense)
Also fix some dubious
except KeyboardInterrupt
which caused for exampleor
(note the
TypeError
!)Component: misc
Author: Jeroen Demeyer
Reviewer: Volker Braun
Merged: sage-5.7.beta2
Issue created by migration from https://trac.sagemath.org/ticket/14028
The text was updated successfully, but these errors were encountered: