Use distinct exit codes for intentional exits #521
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.
Currently, all the intentional application exits look like this:
This causes all exit codes to be
1
. That's the same exit code when an Error is raised. This means, it is impossible to distinguish programmatically, if the application crashed, or halted gracefully. That can be important, when this application is called e. g. from within a script.This pull request fixes this issue, by splitting all
exit(<string>)
occurrences in aprint(<string>)
call, followed by aexit()
with a suitable code from theos
package. For example:I would highly appreciate, if this pull request would be merged. I can't imagine a scenario, where this change has any negative effect.