You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When interrupting a Python kernel in a notebook (Notebook: Interrupt), its child processes (for example those launched via subprocess) don't receive the SIGINT. This is different from how the official Jupyter Notebook does it or how most common shells do it upon CTRL+C, which sends the SIGINT to child processes as well. Is this different behavior intended or is it an omission?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When interrupting a Python kernel in a notebook (Notebook: Interrupt), its child processes (for example those launched via
subprocess
) don't receive the SIGINT. This is different from how the official Jupyter Notebook does it or how most common shells do it upon CTRL+C, which sends the SIGINT to child processes as well. Is this different behavior intended or is it an omission?Beta Was this translation helpful? Give feedback.
All reactions