5 ms·

Show HN: Codebraid – Execute Code Blocks in Markdown (Python, Julia, Rust, R)

22 points by gpoore 8y ago

stfwn 8y ago
This is great! Ever since I briefly worked with .rmd files in combination with RStudio I had it in the back of my mind that it would be nice to have something like it (but lightweight) for Markdown with Python and pipe the output through Pandoc. Jupyter Notebooks are nice, but it gets hacky to use your own editor and the file format is bad for git diffs. I'm definitely going to give Codebraid a solid try.
- cuchoi 8y ago
  RMarkdown supports Python. I haven't used it, so I can't vouch for it but I have heard good things about it.
  - truculent 8y ago
    Rmd + Python is preferable to Jupyter for me. It's still not quite at the level of R support (for obvious reasons) but I think it's good.
- closed 8y ago
  There's also jupytext, which provides round trip conversion between Rmarkdown and jupyter notebooks, so you can edit the markdown in jupyter, or in an editor and have it automatically converted to ipynb!
liquidzoot 8y ago
So org-babel but with pandoc? I'm on board.
- eigenspace 8y ago
  What are the advantages of pandoc over orgs builtin export functionality?
  - rgoulter 8y ago
    Org is essentially tied to Emacs. Which is great if you use Emacs, but means you miss out on that functionality elsewhere. If you're not using Emacs, pandoc is a great tool for converting documents (e.g. to HTML, to PDF). And a tool like codebrain would be useful for imitating some of the functionality that org-babel provides.
- gpoore 8y ago
  Yes, that's one way to describe what I'm hoping to do with this. The focus right now is on markdown, but since Pandoc supports so many input formats, it should be easy to add support for other formats like LaTeX once the markdown features stabilize. There isn't yet an equivalent of org-babel's ability to share data between code blocks, though I hope to add something similar eventually. The next big feature will probably be the ability to name code blocks, and then insert any combination of their code/output/errors at arbitrary other locations in the document.

22 points by gpoore 8y ago

This is great! Ever since I briefly worked with .rmd files in combination with RStudio I had it in the back of my mind that it would be nice to have something like it (but lightweight) for Markdown with Python and pipe the output through Pandoc. Jupyter Notebooks are nice, but it gets hacky to use your own editor and the file format is bad for git diffs. I'm definitely going to give Codebraid a solid try.

cuchoi 8y ago
RMarkdown supports Python. I haven't used it, so I can't vouch for it but I have heard good things about it.
- truculent 8y ago
  Rmd + Python is preferable to Jupyter for me. It's still not quite at the level of R support (for obvious reasons) but I think it's good.
closed 8y ago
There's also jupytext, which provides round trip conversion between Rmarkdown and jupyter notebooks, so you can edit the markdown in jupyter, or in an editor and have it automatically converted to ipynb!

liquidzoot 8y ago

So org-babel but with pandoc? I'm on board.

eigenspace 8y ago
What are the advantages of pandoc over orgs builtin export functionality?
- rgoulter 8y ago
  Org is essentially tied to Emacs. Which is great if you use Emacs, but means you miss out on that functionality elsewhere. If you're not using Emacs, pandoc is a great tool for converting documents (e.g. to HTML, to PDF). And a tool like codebrain would be useful for imitating some of the functionality that org-babel provides.
gpoore 8y ago
Yes, that's one way to describe what I'm hoping to do with this. The focus right now is on markdown, but since Pandoc supports so many input formats, it should be easy to add support for other formats like LaTeX once the markdown features stabilize. There isn't yet an equivalent of org-babel's ability to share data between code blocks, though I hope to add something similar eventually. The next big feature will probably be the ability to name code blocks, and then insert any combination of their code/output/errors at arbitrary other locations in the document.