I have accidentally started a runaway process in ipython notebook, and I had to kill the ipython process. When I stared ipython notebook server again and connected with my browser, suddenly the toolbar labels are missing (see attached screenshot)
I have tried restarting my machine and starting ipython notebook anew, but this did not help.
Can somebody please advise how I can restore the toolbar labels?
Related
I have added a new kernel to my jupyter notebook. It works totally fine using Jupyter in the browser. However if I try to open my notebook in VSCode (and change the kernel) it doesn't show up --> the drop-down menu doesn't show my kernel.
Is there anything I can do to resolve this issue.
Thanks in advance!
I am trying to run a Jupyter notebook in VSCode. I have successfully run notebooks in the past, but something has happened to make VSCode "hang" when I try running. When I hit run, the terminal shows the file location and the location of python.exe as expected (shown in the first image, with some personal information redacted), but nothing ever happens. The code never completes and the cells never output. I get a small "pending" icon of a clock and an arrow (shown in the second image) to tell me a cell is running, but even the most basic "Hello, world" never completes or gives an error. I have no trouble running regular python files, and if I export an ipynb to py I can run it, but I cannot run the ipynb itself. Trying to restart the Jupyter kernel also seems to hang, never completing and never crashing or erroring. The only clue I really have is that when I hit F5 to run, there's no python version showing in the bottom left corner, the way there is when I run py files (third image is while trying to run ipynb and fourth image is while successfully running py).
I have tried uninstalling and reinstalling the Jupyter extension from VSCode and restarting VSCode between every step. I have tried swapping between python.exe and conda.exe in the terminal settings python.condapath. I have checked that the windows terminal is cmd. I've tried creating new notebooks in VSCode that only have print("Hello, world"). I have tried the command "Select interpreter to start Jupyter server" and selected the correct version of Python, but nothing has changed any time I've tried to run.
I am using Anaconda version 4.10.3, VSCode 1.61.2, IPython version 7.9.0, and Jupyter notebook version 6.4.3.
Is there a way to open an IPython interactive console in pycharm that is connected to an existing running kernel (similar to "python --existing")?
btw: in case it's relevant, in my case, the running kernel is of a Jupiter notebook...
EDIT: To clarify, my question is NOT about how to open an interactive console in PyCharm. It is about how to connect that interactive console to a an existing running (Jupiter notebook) Kernel.
(tl;dr: Use jupyter console --existing in the PyCharm "Terminal" tool window (not the "Python Console" tool window) to connect to an existing iPython kernel running in a local Jupyter Notebook server.)
I can confirm that the comment by #john-moutafis suggesting ipython console --existing is the right idea. The command gives "WARNING | You likely want to use jupyter console in the future" so I tried that.
I have a project using a conda environment as its interpreter. Jupyter Notebook is installed in the conda environment.
I open the Terminal tool window. It automatically activates the conda environment.
I type jupyter notebook. The notebook server starts and a browser window opens.
I create a notebook in the browser, and execute a cell containing foo = "bar".
In PyCharm, I open another Terminal tool window by clicking the plus sign to the left of the terminal pane.
In the new terminal I type jupyter console --existing, and it starts an ipython console session.
At the prompt I type dir(), and foo is among the results, confirming that I'm attached to the same kernel as the notebook.
I don't know how it picks which kernel to connect to when there are multiple kernels running in the notebook server.
Don't type exit in the iPython session if you plan to continue using the notebook, it shuts down the kernel.
Unfortunately, tools like Debug and "Execute Line/Selection in Console", which are available for the "Python Console" tool window, are not available for the "Terminal" tool window. In fact, because the Terminal tool window is a simple tool, and that's where I've run my commands, this solution isn't very integrated with PyCharm. The terminal opens in the project directory and activates the conda environment, and it's conveniently adjacent to the editors and tools of the IDE, but otherwise there's no connection to PyCharm's tools.
If anyone can successfully attach PyCharm's integrated PyDev debugger to a running kernel, please chime in.
I'm using PyCharm 2016.3 on macOS 10.12.3.
The easiest way for me is just to type %qtconsole in a jupyter notebook cell and run it. A qt console will open already connected to the running kennel. No PyCharm involved.
My PyCharm freezes after running any code in .ipynb (Jupyter Notebook) file.
i.e. the cell starts running and after that PyCharm doesnt respond and I have to kill it. No message is shown.
.py scripts are running correctly. Can anyone help?
My versions:
PyCharm Community Edition 2016.2.3 (Ubuntu 16.04)
ipython 5.1.0 py35_0
jupyter 1.0.0 py35_3
notebook 4.2.3 py35_0
It appears that your jupyter kernel is not running.
I have had success by first starting a jupyter notebook from the command line:
$jupyter notebook.
Then go back to the PyCharm jupyter notebook and run a cell. If you get the dialog box to enter the Jupyter Notebook URL, enter the url printed to your command line terminal session after you started the notebook there.
I've installed Enthought Canopy 1.3.0.1715 on Max OSX 10.9.2, and updated all packages. All seems to have gone well until trying to create a new iPython notebook. When the notebook opens, none of the buttons for the notebook contain any images (just small 'x''s). II believe this problem is causing other issues in notebooks, but I'd like to get this one fixed first. Has anyone seen this and have a solution / idea? FYI, This works fine starting notebook from the terminal, just not as how Canopy is hosting the notebook.