Preserve caret positions in Python 3.11+ tracebacks #91
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
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #91 +/- ##
==========================================
- Coverage 96.96% 96.64% -0.32%
==========================================
Files 9 9
Lines 758 955 +197
Branches 53 75 +22
==========================================
+ Hits 735 923 +188
- Misses 18 21 +3
- Partials 5 11 +6
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Python 3.11 introduced detailed error locations with caret indicators pointing to the exact expression that caused an exception. When tracebacks are serialized and reconstructed through tblib, this column position information was lost, making debugging reconstructed exceptions harder. This fixes issue ionelmc#76. The solution captures column offsets from traceback objects and embeds them in custom co_linetable bytes when reconstructing code objects. CPython 3.11+ and PyPy 3.11+ use different linetable formats, so separate encoding functions handle each implementation. The fix also ensures __traceback_maker is defined in globals during code execution to prevent NameError at the wrong instruction index, which would capture incorrect column positions from tb_lasti. Add test for __traceback_maker globals bug Without __traceback_maker in the globals dict during exec, the LOAD_NAME instruction raises NameError at tb_lasti=2 instead of RAISE_VARARGS executing at tb_lasti=4. This captures column positions from the wrong bytecode instruction, showing positions for just the name '__traceback_maker' (columns 6-23) instead of the full 'raise __traceback_maker' expression (columns 0-23). This test verifies the fix catches this by asserting the column start is 0, not 6, proving the exception originates from the correct instruction with accurate position information.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Python 3.11 introduced detailed error locations with caret indicators
pointing to the exact expression that caused an exception. When
tracebacks are serialized and reconstructed through tblib, this
column position information was lost, making debugging reconstructed
exceptions harder. This fixes issue #76.
The solution captures column offsets from traceback objects and
embeds them in custom co_linetable bytes when reconstructing code
objects. CPython 3.11+ and PyPy 3.11+ use different linetable
formats, so separate encoding functions handle each implementation.
The fix also ensures __traceback_maker is defined in globals during
code execution to prevent NameError at the wrong instruction index,
which would capture incorrect column positions from tb_lasti.