raise errors
If an error occurs, this is hidden by try-catch
statements. I could write a wrapper to checks the return code, and raises an error, but this is slower, uglier and I lose what error was initially raised, I want to treat a network issue potentially different then SIGINT
.
It seems #14 (closed) requested the opposite, so I am not sure this change would be welcomed, but I think it is much easier to wrap calls in try-except
statements, rather then the other way around. I didn't quite understand the use-case of #14 (closed) why the call couldn't be wrapped in a try-except
statement on the caller side.