🚸 Don't truncate code lines in traceback when formatted with Rich#1695
Open
YuriiMotov wants to merge 2 commits intomasterfrom
Open
🚸 Don't truncate code lines in traceback when formatted with Rich#1695YuriiMotov wants to merge 2 commits intomasterfrom
YuriiMotov wants to merge 2 commits intomasterfrom
Conversation
Contributor
📝 Docs previewLast commit c6ecd8c at: https://20e11721.typertiangolo.pages.dev Modified Pages |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When tracebacks are formatted with Rich, code lines are currently truncated to 88 characters (or less if terminal width is less).
This PR:
Small terminal width (before - after):
After is with
pretty_exceptions_word_wrap=TrueWide terminal (before - after):
If the idea is accepted, I will need to add a test for code example with word wrapping