-
Notifications
You must be signed in to change notification settings - Fork 335
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
Salvaging an IPython session from a frozen Atom #57
Comments
The IPython kernel saves out a file for reconnection — if it's still running, I think you can reconnect to it. When you run a kernel directly, it spits out a message like this:
The file is (for me) saved in |
I just tried this with a kernel started by Hydrogen and it worked. You can even run |
That is interesting. I just gave that a try. It seems I can connect,
but I don't get further than that. Maybe I should say that the python script is still running. I want to interrupt it, pickle as much as I can, and then restart atom. |
Maybe you can send an interrupt to the kernel manually — you can |
Success! Thanks a lot! |
Is there any way I can salvage a still running python backend if Atom locked up completely (but hasn't crashed)? Can I connect the python session to a CLI somehow?
I have been running a program for a while now and I don't want to loose my results.
The text was updated successfully, but these errors were encountered: