[baldfat]

In R we also have notebooks that does this just it is slightly different. RMarkdown is how we do this same thing. At first I missed the different code and text blocks but it is just easier to work with when it is all a text file. You can make the RMarkdown for reports and then just run them from the command line and never have to open RStudio or R. Saves me a ton of time.

You use back ticks to make your code chunks.

For example: Some random Markdown text here is treated as a text block in Juypter

```{r}

summary(cars)

```

Then some further text goes here.

http://rmarkdown.rstudio.com/index.html

[danso]

I agree, though I don't know if I'm just missing something when working in Jupyter, or if Python has an equivalent of RMarkdown?

Jupyter has some conveniences, but the tradeoffs aren't worth it for me. Working in a web browser has much less power, when it comes to keyboarding, than Atom/Sublime. And I generally don't need to interact with my data; I know what I'm outputting, I just want to show the results to readers alongside my code. I don't use RStudio but RMarkdown is easy to run from the command line.

By contrast, Jupyter requires (AFAIK) working within the browser and, when you save the file, you get a huge jumble of JSON, which is how the notebook is serialized. I tend to write a lot of vignettes/explorations and the need to full-text grep them is important to me and is not feasible when the text content is saved as JSON.

[baldfat]

>Jupyter, or if Python has an equivalent of RMarkdown?

You can convert the Notebooks to different formats. Though they tend to have to be fixed up a bit for a script (Which I also might need to in R to turn it into a script)

https://ipython.org/ipython-doc/3/notebook/nbconvert.html