Skip to content
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

Do not capture BdbQuit. #10009

Merged
merged 1 commit into from Oct 17, 2016
Merged

Do not capture BdbQuit. #10009

merged 1 commit into from Oct 17, 2016

Conversation

Carreau
Copy link
Member

@Carreau Carreau commented Oct 15, 2016

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 ?

@Carreau Carreau added this to the 5.2 milestone Oct 15, 2016
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 ipython#10006
@amueller
Copy link

That's raised by calling quit()? And/or by pressing "Ctrl+D"? Then yes.

@minrk minrk merged commit 428e834 into ipython:master Oct 17, 2016
@amueller
Copy link

thanks :)

takluyver pushed 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>
@Carreau Carreau deleted the no-ignore-bdbquit branch February 13, 2017 21:46
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.

None yet

3 participants