search for: e13048fd9

...rror, and needlessly complicates clients to have to add try: blocks. Better is if nbdsh itself prints the same stack trace that python would, but handles the error and exits python cleanly so that ABRT does not think that the exception was unhandled. See https://github.com/libguestfs/nbdkit/commit/e13048fd9 for an example of client cleanup made more verbose if we don't patch libnbd. --- Is it worth a command-line option, off by default, but that the user can opt in to, where the option being set says we re-raise the excpetion instead of handling it ourselves? python/nbdsh.py | 18 ++++++++++++-...

...the problem, and only prints a stack trace when debugging is in effect, but otherwise just prints the error message. In this way, the user is not presented with a wall of python stack trace, and ABRT does not think that the exception was unhandled. See https://github.com/libguestfs/nbdkit/commit/e13048fd9 for an example of client cleanup made more verbose if we don't patch libnbd. --- On IRC, we decided that printing the stack trace can be useful when debugging (if -c triggers calls through some deeply-nested python code), but generally gets in the way for default behavior. python/nbdsh.py |...