In commands, add a separate command error to signal execution errors #74
Labels
Comments
Merged
jonls
added a commit
that referenced
this issue
Jun 24, 2016
Fixes #74 by adding the fail() method on Command which can be used to make the command fail without printing usage information. Optionally, the exception that caused the failure is logged to the debug level.
2 tasks
spikeliu
pushed a commit
to spikeliu/psamm
that referenced
this issue
Jun 29, 2016
Fixes zhanglab#74 by adding the fail() method on Command which can be used to make the command fail without printing usage information. Optionally, the exception that caused the failure is logged to the debug level.
|
Fixed in #96 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently the
CommandErrorexception is available to signal that a command failed. However, this exception causes the argument parser to print out usage information which is only appropriate if the error was caused by incorrect arguments supplied by the user. In other cases, the command may wish to signal an error that does not cause usage information to be printed. Most commands where errors are possible either raise an exception or let an existing exception bubble up. This accomplishes the goal of exiting the command with an error code but does not provide a good error message to the user. Ideally, the stack trace of the exception should be logged (at "debug" level) and a good error message should be logged at "error" level.The text was updated successfully, but these errors were encountered: