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
When a custom exception that does not have a valid str() method is raised, a secondary exception is raised by Rich's excepthook. This is likely a very rare case which might not be worth considering. However, this issue was reported in my own project (aroberge/friendly#181) and I thought I should share it for your consideration.
To Reproduce
After installing rich.traceback, import a file containing the following code:
Read the docs
This is not adressed in the documentation.
Describe the bug
When a custom exception that does not have a valid
str()
method is raised, a secondary exception is raised by Rich's excepthook. This is likely a very rare case which might not be worth considering. However, this issue was reported in my own project (aroberge/friendly#181) and I thought I should share it for your consideration.To Reproduce
After installing rich.traceback, import a file containing the following code:
Using Python's 3.8 repl, here's the output:
As you can see, Python seems to guard againts cases where
str()
fails. Using Rich, the following is generatedPlatform
I'm convinced that the issue is independent of the platform and the terminal type. I'm using Windows and Windows Terminal.
Diagnose
I'm using rich version 9.10.0
The text was updated successfully, but these errors were encountered: