Replace production code asserts with if-based checks and exception raises #70
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
falquaddoomi
approved these changes
Dec 16, 2024
|
Thanks @miltondp and @falquaddoomi ! Merging this in. |
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 PR replaces some production code asserts with if-based checks and exception raises (when appropriate) to simulate the use of assertions without the related risks. It's considered a best practice to avoid the use of asserts in production code as they may be ignored during processing by using the
python -Oflag (optimization mode) and could be replaced with more specific exception types + messages.Thanks for any feedback!
Closes #64