Repository navigation
3.11 backtrace visual indicators are too verbose #93883
Copy link
Copy link
Closed
Labels
type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
Description
Activity
- addedtype-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
on Jun 16, 2022 I've prototyped the change for traceback.py. Making the equivalent change to C traceback code and updating documentation is still required. I'd like to hear if this change has some support from Python devs before putting more time into the PR.
I am very, very keen on this change! Thanks very much @belm0 for thinking of this and implementing a patch 😍
Reacted by John Belmonte, Terry Jan Reedy, Thomas Grainger and dskrypa- added a commit that references this issue
on Jun 24, 2022 PR #93994 is ready for review
- added a commit that references this issue
on Jul 11, 2022 - added a commit that references this issue
on Jul 11, 2022 The refinement is merged and backported to 3.11 for the beta4 release.
Reacted by Alex Waygood, Oleg Iarygin, Zac Hatfield-Dodds and Terry Jan Reedy
Metadata
Metadata
Assignees
Labels
type-bugAn unexpected behavior, bug, or errorAn unexpected behavior, bug, or error
I understand that the new visual indicators can be disabled, but we shouldn't have to choose between guaranteed 50% longer backtraces and pertinent column information.
Often, the visual indicator spans the entire line for a large percentage of the backtrace. (I've seen cases in our app where it's true for 100% of the backtrace.)
Proposal: elide the indicators when they span the whole line
Elide traceback column indicators when the entire line of the frame is implicated. This reduces traceback length and draws more attention to the remaining (very relevant) indicators.
before:
after: