Introduce NotFoundError for backward and forward compatibility #47
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
This change serves as backward and forward compatible with pySBOL swig and native pySBOL. It also serves as better documentation about what the raised error means, and why the code responds the way it does.
|
This is subsumed by #49. |
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.
This change serves as backward and forward compatible with pySBOL swig
and native pySBOL. It also serves as better documentation about what
the raised error means, and why the code responds the way it does.
This pull request only changes
RuntimeErrors that are covered by the unit tests. I don't know which other caughtRuntimeErrors are also covering for object not found.Fixes #46