Skip to content

Conversation

@ivonastojanovic
Copy link
Contributor

The bytecode panel appears when a user generates a heatmap with --opcodes and clicks the button to unfold a line and display the bytecode instructions. Currently, an empty space appears on the left where the line number, self, and total columns are displayed. This area should instead extend those columns, rather than leaving a gap.

Before:

Screen.Recording.2025-12-18.at.00.08.34.mov

Now:

Screen.Recording.2025-12-18.at.00.03.09.mov

The bytecode panel appears when a user generates a heatmap with
--opcodes and clicks the button to unfold a line and display the
bytecode instructions. Currently, an empty space appears on the
left where the line number, self, and total columns are displayed.
This area should instead extend those columns, rather than leaving
a gap.
@pablogsal
Copy link
Member

@lkollar @hugovk @savannahostrowski @StanFromIreland @AA-Turner I am curious what you think about this UX. @ivonastojanovic and myself were discussing how this should look. I particularly like that when you click the arrow it looks like the source line "unfolds" and shows the bytecode internals but the original versions is too wide and the data is too spread around. On the other hand this looks "more" like a popup. What do you folks think?

Copy link
Member

@hugovk hugovk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, this looks better 👍

@pablogsal pablogsal merged commit cbc0851 into python:main Dec 18, 2025
52 checks passed
@pablogsal
Copy link
Member

Amazing 👌

cocolato pushed a commit to cocolato/cpython that referenced this pull request Dec 18, 2025
The bytecode panel appears when a user generates a heatmap with
--opcodes and clicks the button to unfold a line and display the
bytecode instructions. Currently, an empty space appears on the
left where the line number, self, and total columns are displayed.
This area should instead extend those columns, rather than leaving
a gap.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants