3 ms·

The web interface was the main reason I never really used the tool for more than a few test runs. Writing code in the browser combines bad usability and perform

The web interface was the main reason I never really used the tool for more than a few test runs. Writing code in the browser combines bad usability and performance with a lack of useful dev tools. Which brings me to the question whether I can edit the code in a text editor as well or I have to write it as shown in the animation. It would be really helpful if there was a shortcut to open the current (code) section in $EDITOR, kind of like Git and other tools do it.

atoav 6y ago
I used nteract which is like a bit like a notepad for ipnyb files. It is not great software, but it works.
samuell 6y ago
One way I've been exploring, is to use nbconvert [1] to convert notebooks to python scripts and back. [1] https://nbconvert.readthedocs.io/en/latest/index.html https://nbconvert.readthedocs.io/en/latest/index.html
- whitten 6y ago
  Have you found any Jupyter notebooks that don't convert easily ?
nsonha 6y ago
Vscode and intelij both have had good support for notebook for a long time. For the web interface there maybe even extension to add intellisense to it or smt
BiteCode_dev 6y ago
Use the qt-console, best of both worlds.
- klibertp 6y ago
  qt-console is great, but it's not a notebook, ie. you don't have cells you can go back to and edit. It's more of a classic console, with great readline emulation and ability to display images easily.
zokier 6y ago
There is the %edit magic
goerz 6y ago
For editing notebooks in vim, I've created https://github.com/goerz/jupytext.vim https://github.com/goerz/jupytext.vim. Note that this does not allow to run any cells, it just edits the inputs. The motivation behind this was to have some basic interaction with existing ipynb files on a remote server without having to run the jupyter server (and set up port forwarding etc.) It's worth noting that the `jupytext.vim plugin is most useful if you're actually not running `jupytext` within jupyter; If you are, you could just directly open the .py or .md files linked to any .ipynb in your editor. I've used `jupytext.vim` to edit existing notebooks and then run them through `jupyter nbconvert --to notebook --execute`. It's also great for refactoring: moving code from a notebook files into a module, between notebooks, or to create a new notebook as a variation of an existing one.

atoav 6y ago

I used nteract which is like a bit like a notepad for ipnyb files. It is not great software, but it works.

samuell 6y ago

One way I've been exploring, is to use nbconvert [1] to convert notebooks to python scripts and back. [1] https://nbconvert.readthedocs.io/en/latest/index.html https://nbconvert.readthedocs.io/en/latest/index.html

whitten 6y ago
Have you found any Jupyter notebooks that don't convert easily ?

nsonha 6y ago

Vscode and intelij both have had good support for notebook for a long time. For the web interface there maybe even extension to add intellisense to it or smt

BiteCode_dev 6y ago

Use the qt-console, best of both worlds.

klibertp 6y ago
qt-console is great, but it's not a notebook, ie. you don't have cells you can go back to and edit. It's more of a classic console, with great readline emulation and ability to display images easily.

zokier 6y ago

There is the %edit magic

goerz 6y ago

For editing notebooks in vim, I've created https://github.com/goerz/jupytext.vim https://github.com/goerz/jupytext.vim. Note that this does not allow to run any cells, it just edits the inputs. The motivation behind this was to have some basic interaction with existing ipynb files on a remote server without having to run the jupyter server (and set up port forwarding etc.) It's worth noting that the `jupytext.vim plugin is most useful if you're actually not running `jupytext` within jupyter; If you are, you could just directly open the .py or .md files linked to any .ipynb in your editor. I've used `jupytext.vim` to edit existing notebooks and then run them through `jupyter nbconvert --to notebook --execute`. It's also great for refactoring: moving code from a notebook files into a module, between notebooks, or to create a new notebook as a variation of an existing one.