Re:Why Jupyter is data scientists’ computational notebook of...
by bunderbunder on Tuesday October 30, 2018 @10:49AM
(#18336970)
I am very hopeful that JupyterLab will get support for the Language Server Protocol sometime soon. That would make all the difference in the world for me. I'd still have to use a terminal to build and run tests, but I wouldn't be surprised if a test runner comes along fairly quickly after that.
(Relevant issue: https://github.com/jupyterlab/jupyterlab/issues/2163)
Re:Why Jupyter is data scientists’ computational notebook of...
by agibsonccc on Tuesday October 30, 2018 @10:20AM
(#18336669)
Data frame rendering in the various notebooks (beaker,jupyter,zeppelin,..) is wonderful.
Your workflow sounds closest to what I do. If I want to visualize something I tend to compile my thoughts/imports and organize things in an editor first and put it in a notebook in parallel. It helps with version control as well.
Work (and often debug) in jupyter -> open the notebook from pycharm when it's got some completed thoughts and write into a python module + test module, tidying up and adding type annotations.
Sometimes doing that multiple times so that the notebook is importing from modules which were originally pulled out of the notebook.
It sucks having to use two tools but I don't think there's any one tool that can do both as well as pycharm/jupyter, short of me getting a lot better at emacs or writing a lot of custom Atom extensions (I think).