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
This feature request sounds a little stupid, but it is one that I would very much appreciate. During my normal work with notebooks, I restart the IPython kernel quite frequently. It would save me some time, if the restart was faster. Could you implement the following: Instead of having only one IPython kernel running at any point in time, a second, hidden kernel is spawned also. When the "Restart IPython Kernel" button is pushed, the notebook environment immediately switches to the second kernel, making the first kernel hidden. The first kernel dies eventually, and I can continue working immediately.
Would like to hear your thoughts.
Best, Flo
The text was updated successfully, but these errors were encountered:
I agree, this can be useful when we have a script that hangs the kernel.
As a starting point I'd probably use the telemetry to check how often users restart the kernels.
This feature request sounds a little stupid, but it is one that I would very much appreciate. During my normal work with notebooks, I restart the IPython kernel quite frequently. It would save me some time, if the restart was faster. Could you implement the following: Instead of having only one IPython kernel running at any point in time, a second, hidden kernel is spawned also. When the "Restart IPython Kernel" button is pushed, the notebook environment immediately switches to the second kernel, making the first kernel hidden. The first kernel dies eventually, and I can continue working immediately.
Would like to hear your thoughts.
Best, Flo
The text was updated successfully, but these errors were encountered: