You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is currently the default behavior unless the traceback rendering is explicitly disabled.
I think this should be revisited because I'm realizing just how often rich is installed as an incidental dependency. Many users might suddenly be surprised when their stack traces look rad all of a sudden.
Reconsider for 1.1.
The rich tracebacks are only installed if django-typer is installed as an app in INSTALLED_APPS which is unnecessary unless users want to use shellcompletion. This means incidental dependencies on django-typer and rich won't trigger this behavior until and unless the user installs django_typer. Maybe this means its fine?
Let me know what you think!
The text was updated successfully, but these errors were encountered:
bckohan
changed the title
Should rich tracebacks be installed automatically if rich is installed?
Should rich tracebacks be installed automatically if rich is installed and django_typer is in INSTALLED_APPS?
Mar 3, 2024
This is currently the default behavior unless the traceback rendering is explicitly disabled.
I think this should be revisited because I'm realizing just how often rich is installed as an incidental dependency. Many users might suddenly be surprised when their stack traces look rad all of a sudden.
Reconsider for 1.1.
Let me know what you think!
The text was updated successfully, but these errors were encountered: