-
Notifications
You must be signed in to change notification settings - Fork 129
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
theory+likelihood: better error info for internal (or inherited)
- Loading branch information
1 parent
30dc978
commit bb2a0da
Showing
1 changed file
with
6 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bb2a0da
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
there shouldn't be a "not" before isinstance(e, LoggedError): ?
bb2a0da
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally it's the other way around: if we are raising a LoggedError, we are assuming that we know what's happened and we are providing an informative message. Otherwise we should raise a different kind of error, and in that case print the traceback. I think what's wrong is the fix that I suggested for the other case. We don't need the traceback there, just the message ("get_testa NotImplemented in camb") so I'd be in favour of reverting that change there and instead trying to find out how we can show the relevant message. Let me give it a try.