-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
document Keyboard Interrupt will only show a stack trace with --fulltrace #513
Comments
Original comment by Matthias Urlichs (BitBucket: smurfix, GitHub: smurfix): Hi, Yes, that would be great; my system has a pretty deep object hierarchy and I didn't check --full-trace, assuming that it only affects how much of the -- Matthias Urlichs |
Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42): OK. Please note, though, that I am spending my time on reviewing pull requests and implementing features or fixing bugs that are high priority to me. That's requiring quite a lot of my time already. IOW, while i welcome suggestions i also depend on pull requests and people wanting to improve things for their own use cases themselves. |
as noted by the original reporter it was a bit hard to figure |
This issue is identical or closely related to #1366. Should the --fulltrace option be further documented? |
That would be great. Could you open a PR @omarkohl ? 😁 |
Closing this as there's a message when hitting ctrl-c now. |
Originally reported by: Matthias Urlichs (BitBucket: smurfix, GitHub: smurfix)
Sometimes (a test runs very long for no good reason, goes into endless recursion or a loop) I want an interrupt with stack trace / pdb when I press ^C.
Could you please add an option which turns off catching KeyboardInterrupt and handles it like any other error?
The text was updated successfully, but these errors were encountered: