bpo-43008: Make IDLE respect sys.excepthook#24302
Conversation
|
CLA signed, it'll take a bit to update tho. |
Sorry, something went wrong.
terryjreedy
left a comment
There was a problem hiding this comment.
I answered on the issue what is required and desired.
Recording of CLA is also required. Won't happen before Monday at earliest.
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Sorry, something went wrong.
..." and reset display and exception handling".
...when raising in 2-process mode, in a way that matches normal shell behavior.
|
Besides the tests, I have made the requested changes; please review again. I didn't manage to figure out how to go about testing an excepthook in the first place, let alone a good or bad one. Hope that's not an issue. |
Sorry, something went wrong.
|
Thanks for making the requested changes! @terryjreedy: please review the changes made to this pull request. |
Sorry, something went wrong.
|
Thanks @Kenny2github for the PR, and @terryjreedy for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8, 3.9. |
Sorry, something went wrong.
Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu> (cherry picked from commit 7a34380) Co-authored-by: Ken <kenny2minecraft@gmail.com>
Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu> (cherry picked from commit 7a34380) Co-authored-by: Ken <kenny2minecraft@gmail.com>
|
Deleted bogus buildbot splat: test_asyncio altered the execution environment. |
Sorry, something went wrong.
This applies to default 2-process mode as excepthook already works in -n mode.
https://bugs.python.org/issue43008