31–40 of 69 posts
small nitpick : yikes! Jupyter's blog is on Medium :(
Anyone have a quick tldr on the differences between Jupyter Lab, Jupyter Book, and Jupyter Notebooks?
In my job I often have to figure out how to solve a problem involving talking to an API or manipulating data in some way and then sharing that information with others. Jupyter notebooks make that so easy, it’s the first tool that I go to. Being able to mix documentation and code, as well as visualizing output, aligns perfectly with the way I think. I’m not entirely sure I have a use for this book feature, at least no…
I keep my own notes on how to use obscure API features that I've learned, in Jupyter. A colleague of mine, when first introduced to Python and Jupyter, remarked that Jupyter could be a great platform for writing tests.
"MyST Markdown is a superset of Jupyter Markdown (AKA, CommonMark), " Hey Jupyter guys, can you please support asciidoc instead of inventing another MD format.
Earlier quoted context omitted.
This is interesting, so do you think the JupyterBook solution could/should replace nbconvert? I was always a bit frustrated by the way nbconvert pulled in pandoc as a dependency, but then didn't make use of any of its power (pandoc surely has a powerful AST). Instead they re-implemented filters and templates themselves. It struck me that it would have been much cleaner to write a proper 'ipynb > AST' Pandoc reader, a…
In fact, pandoc now does have an ipynb reader and writer. You can convert between ipynb and any of the formats pandoc supports, and you can manipulate the AST using filters.
Earlier quoted context omitted.
>I've done this to directly generate branded PDF reports via latex. Can you elaborate on this a little? Do you mean via Jupyter notebooks?
Yes, via Jupyter notebooks -- using the same machinery that gives the 'File > Export Notebook As...' functionality. My method is roughly this: 1. Create a Python package that subclasses nbconvert.exporters.LatexExporter -- in the setup.py you register the class to 'nbconvert.exporters' in the 'entry_points' dict. 2. You can do general filtering/compiling by registering 'Exporter.filters'. The compile process can be m…
small nitpick : yikes! Jupyter's blog is on Medium :(
small nitpick : yikes! Jupyter's blog is on Medium :(
Yeah, but unfortunately we haven't found anything that allow easy collaboration with folks who don't know how to use GitHub, and migrating away from medium is a paiiin. Though if you have a solution, I would be happy to push for it on the Jupyter side.
Earlier quoted context omitted.
This is interesting, so do you think the JupyterBook solution could/should replace nbconvert? I was always a bit frustrated by the way nbconvert pulled in pandoc as a dependency, but then didn't make use of any of its power (pandoc surely has a powerful AST). Instead they re-implemented filters and templates themselves. It struck me that it would have been much cleaner to write a proper 'ipynb > AST' Pandoc reader, a…
In fact, pandoc now does have an ipynb reader and writer. You can convert between ipynb and any of the formats pandoc supports, and you can manipulate the AST using filters.