Closed antipisa closed 4 years ago
@antipisa - which version of pyq-kernel are you using? Can you reproduce your issue (slow response to SIGINT) in plain pyq, without the jupyter machinery loaded?
Stale issue message
No response from OP to the follow-up questions. Closing.
Versions: PyQ 4.1.13 Python 2.7 kdb+ 3.5
I have noticed that trying to kill a python call in PyQ is significantly slower than killing it in Python. I am wondering how interrupting a python process running on PyQ kernel differs to interrupting a plain python process on jupyter. I understand that it is a python process running on a kdb+ instance, but trying to stop a running cell either causes the session to hang or remains idle. Does ctrl+C on a python process on PyQ send a SIGINT to the underlying kdb session? If so, is there any way to map ctrl+C to comint-interrupt-subjob so that Python can raise a KeyboardInterrupt exception and leave the kdb process intact?