Locals in the stacktrace #295
Open
Conversation
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
Member
|
I like it, but maybe we should also have the ability to disable it from |
Member
Author
Yup, that's an idea. I can add it (maybe I will first decide if it's time to rewrite the libcontext to be coherent and useful) |
Member
Can you disable it once we have called |
MrIndeciso
approved these changes
Dec 23, 2025
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.
This is a proposal to add visualization of local variables in the stack trace, as offered by
rich.traceback(which we already use).Rationale: We will always have at least the debugger available as a local variable, so printing it would be helpful when errors occur, making it easier to spot asymmetry mistakes.
Drawback: This will make the stacktrace even bigger.