Reply to thread

Message

[QUOTE="Steven D'Aprano, post: 5102510"]
[emphasis added]

Yes, really.

Tracebacks are not that unfriendly, generally speaking. In my experience,
the average non-technical person is no more confused and distressed by a
traceback extending over thirty lines than they are by a one line error
message. As the developer, I should see the tracebacks by default[1]. If
I want to suppress or simplify them, then I should take explicit steps to
do so, either by catching the exception and calling sys.exit myself, or
at least by setting a runtime config option to the library.

This also allows me to enable debugging in my app by showing tracebacks,
or disable it by hiding them. That should be my decision, not the
library. If the library catches exceptions then exits, throwing away
potentially useful information, that makes it difficult to debug anything
relying on the library.

I'm willing to concede that, just maybe, something like argparse could
default to "catch exceptions and exit" ON rather than OFF.

[1] There's something in the Zen of Python about that...
[/QUOTE]

Verification