-
-
Notifications
You must be signed in to change notification settings - Fork 32k
bpo-36368: Ignore SIGINT in SharedMemoryManager servers. #12483
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
bpo-36368: Ignore SIGINT in SharedMemoryManager servers. #12483
Conversation
FYI: I could not simulate a console |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See 2 comments
You may want to rebase/merge this. Also, feel free to ping when you need a core review :-) |
ec3cfdc
to
01a1c0f
Compare
Rebased. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
@pierreglaser I think this merged PR was not for the right BPO. https://bugs.python.org/issue36338 is "urlparse of urllib returns wrong hostname" |
@matrixise sorry to hear that. The issue number looks correct though. Maybe I mistyped it when I opened the PR and quickly fixed it afterwards. Is there any way I can help fix that? |
just take care for the next time ;-) I just wanted to check my tests with your PR for that BPO and the tests have failed ;-) I think there is no fix for this issue because your PR has been merged into master. Thanks again for your PR and your contribution. |
When starting a
SharedMemoryManager
in an interactive session, anyKeyboardInterrupt
event will be transmitted to the (sub)process running the shared memory server, which causes theManager
to be unusable thereafter.This PR catches
SIGINT
signals in server processes.https://bugs.python.org/issue36368