August 2, 2021How to Make a Traceback Less Verbose in Jupyter NotebooksFor a project I wanted to try out something new - using Jupyter Notebook to document its XML-RPC API, so documentation and specification cannot drift apart. This worked out great. Except - as the API also has to handle invalid input, Jupyter Notebook shows - correctly - the traceback. The traceback is super verbose. request server.get_licenses("not-existing-id") current print out in Jupyter Notebook --------------------------------------------------------------------------- Fault Traceback (most recent call last) <ipython-input-5-366cceb6869e> in <module> ----> 1 server....