3 ms·

This is amazing. I think ipython notebook is fantastic in all regards. However, I feel there's a bit of an elephant in the room. The main tools I use as a progr

This is amazing. I think ipython notebook is fantastic in all regards. However, I feel there's a bit of an elephant in the room. The main tools I use as a programmer are shell and a text editor. I'm not about to start writing code in a web browser[1]. Is there any hope that there will be a good workflow for somehow editing .ipynb from a text editor or is that antithetical to the design? Could markdown perhaps be used as a primary editing format to target ipynb? Looks like there's at least one project doing that. https://github.com/aaren/notedown https://github.com/aaren/notedown And there's the emacs-specific project https://github.com/tkf/emacs-ipython-notebook https://github.com/tkf/emacs-ipython-notebook [1] EDIT: I mean, not right now anyway. I've got a feeling that statement could seem a bit dated later in my life...

idunning 12y ago
It is an interesting point. In my usage, I don't view it as a one-or-the-other proposition. I use Julia, so if I'm doing some exploratory work and experimentation, or making something to present results, then the IJulia notebook is great. If I'm writing some serious longer-running stuff, or a package, I'm in an editor. Sometimes I'll write code in a separate file and call it from a notebook just to keep the notebook focussed on communicating something, and "hiding" the details.
- ngoldbaum 12y ago
  Yeah, notebooks are great for experimentation but not so much for anything that needs to be reused. I tend to write prototype code in the notebook then copy/paste it into a package as I become satisfied that the code is correct.
wodenokoto 12y ago
Jetbrains also have support https://www.jetbrains.com/pycharm/help/ipython-notebook-support.html#d78773e122 https://www.jetbrains.com/pycharm/help/ipython-notebook-supp...
julienchastang 12y ago
I've been a big fan of TFK's EIN. Unfortunately, TFK no longer maintains the project and I have not had good luck with the various EIN forks. (Anyone else having better experiences?) I still get by with the original EIN by using older versions of ipython/IPyNB. Moreover, the IPyNB technology is getting somewhat bloated with widgets and whatnot and I don't know how that will integrate with an emacs environment. Nevertheless, I still hope emacs modes similar to EIN will be forthcoming in this area. I was hoping to propose a code sprint on this topic at SciPy this year, but I won't be going to Austin, alas.
aaren 12y ago
I wrote notedown precisely so that I could edit notebooks in my text editor and version control them as plain text. It would be good to be able to transparently edit a .ipynb in a text editor - I've been meaning to wrap notedown in a vim plugin but haven't had time. This still leaves the version control problem though. Note that I recently enabled the reverse (editing markdown in the browser as if it was a notebook), enabled by setting the following in ~/.ipython/profile_default/ipython_notebook_config.py (or similar): c.NotebookApp.contents_manager_class = 'notedown.NotedownContentsManager' This is useful for more interactive work, e.g. iterating on plots, whilst still having everything stored in markdown. See [1] for more info. [1]: https://github.com/aaren/notedown/issues/22 https://github.com/aaren/notedown/issues/22

idunning 12y ago

It is an interesting point. In my usage, I don't view it as a one-or-the-other proposition. I use Julia, so if I'm doing some exploratory work and experimentation, or making something to present results, then the IJulia notebook is great. If I'm writing some serious longer-running stuff, or a package, I'm in an editor. Sometimes I'll write code in a separate file and call it from a notebook just to keep the notebook focussed on communicating something, and "hiding" the details.

ngoldbaum 12y ago
Yeah, notebooks are great for experimentation but not so much for anything that needs to be reused. I tend to write prototype code in the notebook then copy/paste it into a package as I become satisfied that the code is correct.

wodenokoto 12y ago

Jetbrains also have support https://www.jetbrains.com/pycharm/help/ipython-notebook-support.html#d78773e122 https://www.jetbrains.com/pycharm/help/ipython-notebook-supp...

julienchastang 12y ago

I've been a big fan of TFK's EIN. Unfortunately, TFK no longer maintains the project and I have not had good luck with the various EIN forks. (Anyone else having better experiences?) I still get by with the original EIN by using older versions of ipython/IPyNB. Moreover, the IPyNB technology is getting somewhat bloated with widgets and whatnot and I don't know how that will integrate with an emacs environment. Nevertheless, I still hope emacs modes similar to EIN will be forthcoming in this area. I was hoping to propose a code sprint on this topic at SciPy this year, but I won't be going to Austin, alas.

aaren 12y ago

I wrote notedown precisely so that I could edit notebooks in my text editor and version control them as plain text. It would be good to be able to transparently edit a .ipynb in a text editor - I've been meaning to wrap notedown in a vim plugin but haven't had time. This still leaves the version control problem though. Note that I recently enabled the reverse (editing markdown in the browser as if it was a notebook), enabled by setting the following in ~/.ipython/profile_default/ipython_notebook_config.py (or similar): c.NotebookApp.contents_manager_class = 'notedown.NotedownContentsManager' This is useful for more interactive work, e.g. iterating on plots, whilst still having everything stored in markdown. See [1] for more info. [1]: https://github.com/aaren/notedown/issues/22 https://github.com/aaren/notedown/issues/22