Why are you using a notebook and an IDE? I thought the notebook UI was an alternative to the IDE UI.
Jupyter notebooks in the IDE: VS Code vs. PyCharm
11–20 of 62 posts
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#12Why are you using a notebook and an IDE? I thought the notebook UI was an alternative to the IDE UI.
I'd compare it loosely to taking notes by hand on a tablet. There is benefit in both, when they are combined it can be a better tool than either alone.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#13Why are you using a notebook and an IDE? I thought the notebook UI was an alternative to the IDE UI.
In my case? pycharm for code completion, debugging, refactoring, etc and notebooks for recording reproducible data analysis steps.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#14Needs 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.
I'm curious if there is an objective breakdown of emacs org mode and other methods. I'd suspect emacs penetration is not terribly high due to initial learning curve.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#15I'm trying to implement these same features in my app, Repla, but without requiring an editor plugin, and instead having a view in a separate app that automatically updates via file-system events when you save. There's some more information here https://repla.app/live-coding.html
It's an approach that I think has somes pros and cons relative to integrating these features into an IDE. The main argument for moving them to a separate app, is that IDEs are already really complicated.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#16Why are you using a notebook and an IDE? I thought the notebook UI was an alternative to the IDE UI.
The IDE (I also use PyCharms) is great for editing code (search, refactoring, syntax highlight...)
Jupyter notebooks (or JupyterLab in my case) is great for prototyping and data visualisation.
In my work (data engineering and training deep neural nets) I also happen to use both. It's unwieldy, but I can't get rid of either one (pycharms or jupyter lab)
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#17Why are you using a notebook and an IDE? I thought the notebook UI was an alternative to the IDE UI.
Frankly I HATE web based notebooks. I do deep learning research, and I write a lot of complex functions to handle pre-processing. And with that there's a lot of debugging I need to do, particularly visual debugging of images. The interactivity of notebooks and the features of an IDE has made my programming experience much better.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#18KDE's Cantor isn't too bad either, but I am not sure how well it interoperates with Jupyter notebooks.
Overall its pretty good but some known issues. See:
https://sirgienkogsoc2019.blogspot.com/2019/08/cantor-and-su...
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#19Microsoft have released another IDE with notebook support called Azure Data Studio. It uses the same underlying code base as VS Code but is targeted at data driven tasks such as connecting to databases.
Strangely, it uses a different jupyter notebook implementation to VS Code. I found it avoids some of the annoying bugs mentioned in another comment.
It also introduces a SQL kernel which I’ve found useful for organising my queries.
Re: Jupyter notebooks in the IDE: VS Code vs. PyCharm
#20Why are you using a notebook and an IDE? I thought the notebook UI was an alternative to the IDE UI.
In my case? pycharm for code completion, debugging, refactoring, etc and notebooks for recording reproducible data analysis steps.
I feel like this is the only sane way to go about things. I really don't understand people using notebooks to actually develop code and train ML/deeplearning models. A real IDE like Pycharm is so much more powerful at debugging, refactoring and in-general, writing good code, structuring it, and not to mention, being able to version control it in a sane manner.