Please disable pretty_exception_enable by default

[LucaBonfiglioli]

First Check

• I added a very descriptive title here.
• I used the GitHub search to find a similar question and didn't find it.
• I searched the Typer documentation, with the integrated search.
• I already searched in Google "How to X in Typer" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to Typer but to Click.

Commit to Help

• I commit to help with one of those options 👆

Example Code

import typer
voglio_morire = typer.Typer(name="voglio_morire", pretty_exceptions_enable=False)

Description

Exception pretty printing is harmful and completely useless in basically every situation I can think of. Plus, it's not safe to turn it off by simply passing:

pretty_exceptions_enable=False

Because this will add an implicit dependency to your code: in order to do this you need to have typer>=0.7, otherwise, an error will be raised. The easiest solution is to manually check the typer version, and then disabling the option if it is >= 0.7

Pretty print exception only works in toy examples when the stack has a depth of 1 to 3, unless you like to have your terminal completely cluttered with magical rainbow stuff, which more often than not exceeds the tty length, you should not use this in a real-world scenario. Please disable it by default.

Operating System

Linux, Windows, macOS, Other

Operating System Details

No response

Typer Version

=0.7

Python Version

Any

Additional Context

No response

[pamelafox]

I am finding myself turning it off as well, as the tracebacks have such depth as to be overwhelming. I'm not sure if there's a bug that's resulting in really high depth tracebacks or if that's to be accepted (even in "short" mode), but I'm going to disable entirely.
I'm curious what the experience is like across developers as a whole with the tracebacks, across developers of new/int/advanced experience.

[dyollb]

I also wanted to disable rich exception handling, since its so annoying to always scroll and carefully search for the source of the exception (see example below).

In the documentation, it says this feature is only active if you install the optional dependency rich, however if I do pip install typer rich is also installed. If I remove rich I get an error.

Example pretty exception

[BeCracked]

I also find myself disabling pretty exceptions when developing. This is mainly because my IDE (PyCharm atm) allows me to click the lines in the traceback with the plain Python tracebacks. This is not the case with the rich tracebacks. Not really rich's fault, but it is how it is.

[albalamia]

You can install the minimal version which does not come with Rich
pip install typer-slim

[dyollb]

Thanks @albalamia i didn't see this in the documentation! This solves the issue for me

[tiangolo]

Thanks for the screenshot @dyollb! This was very illustrative of the problem. I decided to change the default because of this. 🤓