-
-
Notifications
You must be signed in to change notification settings - Fork 34.7k
gh-106670: Allow Pdb to move between chained exceptions #106676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 11 commits
d39fbce
920af94
d24ed3c
63a7347
66a3944
b4f79ad
e3b9e4a
948551c
9ba7bb8
3514edc
4e57c32
9e7354b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -189,6 +189,14 @@ typing | |
| check whether a class is a :class:`typing.Protocol`. (Contributed by Jelle Zijlstra in | ||
| :gh:`104873`.) | ||
|
|
||
|
|
||
|
AlexWaygood marked this conversation as resolved.
Outdated
|
||
| pdb | ||
| --- | ||
|
|
||
| * Add ability to move between chained exceptions during post mortem debugging in :func:`~pdb.pm` using | ||
| the new ``exceptions [exc_number]`` command for Pdb. (Contributed by Matthias | ||
| Bussonnier in :gh:`106676`.) | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry one last nit. The modules here are sorted alphabetically, so this needs to be between path lib and sqlite.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No problem, done and rebased/squashed a bit for a cleaner history.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Please don't use rebases or squashes on CPython PRs, when you can help it :) It interacts badly with the GitHub UI, making it hard for reviewers to see what changed between commits. Everything in CPython is squash-merged anyway, so we really don't care about messy commit history within PRs.
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks. In the future don't squash. We squash on merge anyway, so the commit history doesn't end up in the commit log. But it's useful to have it on the PR, and it's easier to review just the last commit and see what you've changed.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ok, I can also un-squash as well I have the reflog. |
||
|
|
||
| Optimizations | ||
| ============= | ||
|
|
||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.