Pass FileNotFoundError exceptions in likelihood through #201
Conversation
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
|
We plan to update the current likelihood factory scripts to provide likelihood factory functions. Until we do that, this is already a step in the right direction. |
marcpaterno
approved these changes
Oct 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a likelihood raises a
FileNotFoundError, for example due to a missingsaccfile, that exception gets reraised as anImportErrorwith the likelihood file name and buries the actual missing file way up in the trace. See #173 and #175.This PR removes the
try...exceptblock aroundspec.load.exec_module.FileNotFoundErrornow gets passed through correctly. If the actual module cannot be found, that still raises an informative exception.