Skip to content

Conversation

gaogaotiantian
Copy link
Member

@gaogaotiantian gaogaotiantian commented May 4, 2024

We had some discussion in #111744 and in discord channel. We know this is a breaking change but people agree it's much more intuitive.

This basically changes the breakpoint() and pdb.set_trace() behavior so it stops immediately after the call, rather than before the next line.

Unfortunately a lot of the test cases need to be adapted.


📚 Documentation preview 📚: https://cpython-previews--118579.org.readthedocs.build/

@brandtbucher
Copy link
Member

this is a breaking change

Haha.

Away from my computer now, but I’ll take a look at this today.

@brandtbucher brandtbucher self-assigned this May 4, 2024
@gaogaotiantian
Copy link
Member Author

this is a breaking change

Haha.

Pun is actually not intended. Took me a second to realize what's funny :)

@ambv
Copy link
Contributor

ambv commented May 4, 2024

This is a breaking change but I can't tell you how many times I wanted to look at the state of a function, I put breakpoint() at the last line... and it stopped after leaving the function altogether 😵‍💫

So this is great to see!

@brandtbucher
Copy link
Member

Test changes look good. Thanks for applying a variety of fixes there.

Copy link
Member

@brandtbucher brandtbucher left a comment

Choose a reason for hiding this comment

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

Thanks for this! I'll leave it open for a bit in case others have thoughts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants