Repository navigation
Use exit 2 on crash to signal this is no ordinary error - #5987
Merged
Merged
Conversation
Contributor
|
One small suggestion: Use an "abnormal" return value like 255 for crashes. This leaves the door open for distinguishing between several "normal" types of type-checking errors at a later date. (For example, syntax errors vs. type errors.) |
Member
Author
I'm not a big fan of that -- there's no standard for such error codes, while using 2 for "not even wrong" types of errors is at least an old tradition. See also #5982. |
ilevkivskyi
approved these changes
Dec 2, 2018
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The wrapper script we use to run mypy at Dropbox will greatly benefit from this -- it will be able to distinguish between a crash and type-checking errors.