Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upDo not capture BdbQuit. #10009
Merged
Do not capture BdbQuit. #10009
Conversation
If one want to exit Pdb cleanly, it is possible to just use `continue` (or `c`) that will keep up until a potential next invocation. Quit is _meant_ to raise an error. Closes #10006
|
That's raised by calling |
|
thanks :) |
takluyver
added a commit
that referenced
this pull request
Jan 12, 2017
If one want to exit Pdb cleanly, it is possible to just use `continue` (or `c`) that will keep up until a potential next invocation. Quit is _meant_ to raise an error. Closes 10006 --- Thanks amueller for the report. Would that suit you ? Signed-off-by: Thomas Kluyver <thomas@kluyver.me.uk>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If one want to exit Pdb cleanly, it is possible to just use
continue(or
c) that will keep up until a potential next invocation.Quit is meant to raise an error.
Closes #10006
Thanks @amueller for the report. Would that suit you ?