Petr Stanislav

The workaround is to save `iPython._showtraceback` before installing `rich.traceback` and then revert it after installing. ```python ip = get_ipython() ip__showtraceback = ip._showtraceback rich.traceback.install(...) ip._showtraceback = ip__showtraceback ``` The workaround is...

Same behavior in Databricks, issue #2455

For me the `rich.traceback` does not work in Databricks because it prevents detecting an error by Databricks, i.e., the issue in the code does not cause a notebook cell execution...

In the image below, you can see the difference. In the first cell, the Databricks properly catch the exception and highlight the error cell, i.e., stop the execution of the...

@noklam The color is not a problem at all. The problem is running following cells, see video below https://user-images.githubusercontent.com/1212845/182611372-bc126401-5139-4d42-b645-1d899e7ea80b.mov Same for Kedro project and orchecstration.

@AntonyMilneQB and @noklam for Jupyter/Databricks notebook workaround **#1** does not work because `sys.excepthook` is not replaced, see https://github.com/Textualize/rich/blob/2ba277ac54a153d3030b496698133ec2e4f67e1d/rich/traceback.py#L137-L146 What is working is to save `iPython._showtraceback` before installing `rich.traceback` (i.e., before...

@AntonyMilneQB It reverts the visual appearance of the error in the cell, but it does not fix the problem with the error.  >...

@AntonyMilneQB same result (original formatting of the error but still ignoring it), but with the message after importing ```python /databricks/python_shell/scripts/PythonShell.py:46: ImportWarning: PythonShell.py is a launch script, which shall not be...

+1