bpo-36368: Ignore SIGINT in SharedMemoryManager servers.#12483
Conversation
|
FYI: I could not simulate a console |
Sorry, something went wrong.
jdemeyer
left a comment
There was a problem hiding this comment.
See 2 comments
Sorry, something went wrong.
|
You may want to rebase/merge this. Also, feel free to ping when you need a core review :-) |
Sorry, something went wrong.
ec3cfdc to
01a1c0f
Compare
May 10, 2019 17:44
|
Rebased. |
Sorry, something went wrong.
pitrou
left a comment
There was a problem hiding this comment.
LGTM.
Sorry, something went wrong.
|
@pierreglaser I think this merged PR was not for the right BPO. https://bugs.python.org/issue36338 is "urlparse of urllib returns wrong hostname" |
Sorry, something went wrong.
|
@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? |
Sorry, something went wrong.
|
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. |
Sorry, something went wrong.
When starting a
SharedMemoryManagerin an interactive session, anyKeyboardInterruptevent will be transmitted to the (sub)process running the shared memory server, which causes theManagerto be unusable thereafter.This PR catches
SIGINTsignals in server processes.https://bugs.python.org/issue36368