Jupyter notebooks in the IDE: VS Code vs. PyCharm
towardsdatascience.com
Jupyter notebooks in the IDE: VS Code vs. PyCharm
1–10 of 62 posts
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#2Also available at https://github.com/mwouts/notebooks_in_vscode_and_pycharm_ja...
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#3Anyone else noticed that when editing a notebook in VS Code, one could lose unexecuted edits to a cell with accidental arrow key input (that defocuses the current cell and erases changes)? Too many times I have lost a paragraph worth of Markdown text midst typing, it’s kind of maddening.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#4This misses a pretty stellar entrant in the field, Atom + Hydrogen. Works nicely with multiple kernels (I use R and Python), allowing notebook-like functionality across multiple languages.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#5This misses a pretty stellar entrant in the field, Atom + Hydrogen. Works nicely with multiple kernels (I use R and Python), allowing notebook-like functionality across multiple languages.
What do you mean misses? The author mentions that exact combination in paragraph 4.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#6This misses a pretty stellar entrant in the field, Atom + Hydrogen. Works nicely with multiple kernels (I use R and Python), allowing notebook-like functionality across multiple languages.
What do you mean misses? The author mentions that exact combination in paragraph 4.
You're right, I missed that, thanks for pointing it out. I wish it had ranked high enough for a comparison though, seems to solve some of the issues raised (though perhaps causes others).
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#7Anyone else noticed that when editing a notebook in VS Code, one could lose unexecuted edits to a cell with accidental arrow key input (that defocuses the current cell and erases changes)? Too many times I have lost a paragraph worth of Markdown text midst typing, it’s kind of maddening.
Yep - it's very annoying but for me it only happens with markdown cells? So now I generally select all and copy now before leaving a markdown cell if I've edited it.
The other issue is the language server seems to get into a funk regularly - the completion stops working as does the display of docstrings so I regularly use the "Developer: reload window" feature to reset everything.
Also the plots view is poor - it's basically just an SVG you can magnify - there's no proper zoom or rotation for 3d plots.
I was also irritated by the "smart" environment discovery stuff - just let me specify which python install or vent I want to use. Don't make be google to see what names/locations I have to use in order for an environment to magically appear in the list.
Also the editor extension (I use vi mode) is ignored. And even saving the notebook doesn't work the way every other editor pane works in vscode.
Hmm... writing this list makes me wonder why I haven't looked at alternatives.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#8Spyder has a Jupyter notebook plugin. I was able to get a notebook going and link the kernel to the IDE. The variable editor worked and I could debug code in Spyder and then paste it into the notebook. The notebook piece of it was good for graphics, widgets, markdown, etc.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#9Needs more mention of emacs and org mode... :)
I am curious to see the general workflow expanded on. I hesitate to think there is a single correct way to keep a notebook. Seems flexibility is the key feature. And is why text is so well used.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#10KDE's Cantor isn't too bad either, but I am not sure how well it interoperates with Jupyter notebooks.