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
As it truncates the full stacktrace line at certain characters, it becomes inconvenient for users to see which file to look at. I suggest we should not wrap them inside a box.
The text was updated successfully, but these errors were encountered:
It's the width of the code or the width of the terminal that defines how much space is used for the traceback (whichever is smaller). To make the traceback wider so it doesn't wrap, set width to your desired value, or set it to None to use all available width. See traceback docs.
However, with width=None log messages are still truncated at the terminal width. I think there should be a way (i) to disable boxes or (ii) to print the whole line wrapped and continued on the next line.
rich.traceback
makes stacktrace nicer but it wraps everything in 80 characters.For example, see a screenshot in your blog post -- https://www.willmcgugan.com/blog/tech/post/better-python-tracebacks-with-rich/.
As it truncates the full stacktrace line at certain characters, it becomes inconvenient for users to see which file to look at. I suggest we should not wrap them inside a box.
The text was updated successfully, but these errors were encountered: