Live data from Hacker News

Jupytext: Jupyter notebooks as Python scripts

github.com

21–30 of 42 posts

Re: Jupytext: Jupyter notebooks as Python scripts

#21
The Python script can be opened with PyCharm

This is going to be a bit pedantic, but for anyone that doesn't realize. Pycharm can already open ipynb files, and it will connect to a running notebook. I don't do it very often, usually just to quickly find my way around some library code.

This project looks great though. I will likely use it, as I tend to use Jupyter to work out code before copying it over to my main project.

Re: Jupytext: Jupyter notebooks as Python scripts

#22
post #15

This is really cool stuff. Editing notebooks in the browser is pretty good, but it can't (yet) match the experience of a well configured (and extended) text editor.

I've been using vscode with the jupyter extension ( https://github.com/DonJayamanne/vscodeJupyter ) and it's exactly what you describe, experience of a good text editor and the visual notebook workflow.

Neat, I'll give that a shot. Does it handle all kernels?

Re: Jupytext: Jupyter notebooks as Python scripts

#23
post #13

Earlier quoted context omitted.

I think that’s called IPython. But I agree with your sentiment.

I was not being ironic. Notebooks are lovely as an output format for showing your research and allowing others to fiddle with your code. However, for people who do not want to edit inside a web browser window, jupytext is a godsend!

At that point you should put most of your work in a separate file, and just import the stuff you need for your demo.

Re: Jupytext: Jupyter notebooks as Python scripts

#24

This seems neat, but also a bit strange. Are Jupyter notebooks so prevalent that it makes sense to ghave an exporter that makes them into markdown and back again? I mean, I always thought this workflow was neat, but isn't one of the selling points of jupyter the WYSIWYG Interface? And if you like working in code, would it not be easier to create a markdown extension for embedded code (Or does something like this alre…

As an academic, ipython notebooks are becoming the lingua franca of reproducible research. I don’t like it or them, but they’re excellent for didactic purposes. Extracting the code from the markdown is very helpful for me, as I prefer working directly with it most of the time.

Re: Jupytext: Jupyter notebooks as Python scripts

#25
post #15

Earlier quoted context omitted.

I've been using vscode with the jupyter extension ( https://github.com/DonJayamanne/vscodeJupyter ) and it's exactly what you describe, experience of a good text editor and the visual notebook workflow.

Neat, I'll give that a shot. Does it handle all kernels?

It doesn't appear to. Helpfully, Hydrogen [0] for Atom was designed to be entirely language agnostic.

[0]: https://github.com/nteract/hydrogen

Re: Jupytext: Jupyter notebooks as Python scripts

#26
post #14

Earlier quoted context omitted.

> So where is my markdown with embedded code WYSIWYG editor that saves into plain text files? ;-) It's here: https://github.com/gregsexton/ob-ipython

Well, yeah. Org mode can do anything, right? If only it wasn't so tightly coupled to emacs. Not a hater btw, I just can't get used to the editor. The concept of an extendable editor sounds really good, but it just seems so complicated and uncomfortable to use...

If you are used to vim maybe spacemacs can help you?

Re: Jupytext: Jupyter notebooks as Python scripts

#27
post #3

Can someone provide me a usecase for this when compared to executing jupyter straight into VSCode/Atom with vscodeJupyter/Hydrogen?

In the medium term, it's likely that Hydrogen will be able to read and write .ipynb files. It can currently export .ipynb files but has some bugs [0].

[0]: https://github.com/nteract/hydrogen/issues/1296

Re: Jupytext: Jupyter notebooks as Python scripts

#28

This seems neat, but also a bit strange. Are Jupyter notebooks so prevalent that it makes sense to ghave an exporter that makes them into markdown and back again? I mean, I always thought this workflow was neat, but isn't one of the selling points of jupyter the WYSIWYG Interface? And if you like working in code, would it not be easier to create a markdown extension for embedded code (Or does something like this alre…

As an academic, ipython notebooks are becoming the lingua franca of reproducible research. I don’t like it or them, but they’re excellent for didactic purposes. Extracting the code from the markdown is very helpful for me, as I prefer working directly with it most of the time.

I'm sure notebooks are used a lot for interactive exploration, but I would not use them for reproducible research, so long as they lack things like dependency tracking:

https://twitter.com/joelgrus/status/1033035196428378113

Re: Jupytext: Jupyter notebooks as Python scripts

#29

Earlier quoted context omitted.

As an academic, ipython notebooks are becoming the lingua franca of reproducible research. I don’t like it or them, but they’re excellent for didactic purposes. Extracting the code from the markdown is very helpful for me, as I prefer working directly with it most of the time.

I'm sure notebooks are used a lot for interactive exploration, but I would not use them for reproducible research, so long as they lack things like dependency tracking: https://twitter.com/joelgrus/status/1033035196428378113

The bar in academia (over-generalizing here) was so low for so long that anything around including your code with your publication still gets placed under the historical title of "reproducibility" - that's probably where the confusion here is arising. I agree with your sentiment, but grandparent probably just meant "a lot of people release their code as notebooks".
Post reply on HN