Earlier quoted context omitted.
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…
Wow someone use the features I wrote years ago ! <3 You might want to submit a blog post to Jupyter.org to show that this is possible and make it more known.
The new Jupyter Book
41–50 of 69 posts
Re: The new Jupyter Book
#42small nitpick : yikes! Jupyter's blog is on Medium :(
I’m out of the loop. What’s wrong with Medium?
- captures creativity into a centralized proprietary platform on which creators have no control
- modal dialogs nagging you to create an account when you just want to read an article
- uniform, soulless, dull visual design
- heavy pages loaded with JavaScript that don't add any value for the reader
Re: The new Jupyter Book
#43small 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.
Re: The new Jupyter Book
#44I wish that the notebooks supported Typescript or C# or something I'm more familiar with, out of the box. For C# I have LinqPad, which I'm a huge fan of but never discovered something with similar functionality for typescript. I've seen some open source kernels[0] but I'm not sure about the quality, did anyone try them? Deno core in Jupyter would have been amazing. [0]: https://github.com/jupyter/jupyter/wiki/Jupyter…
Re: The new Jupyter Book
#45"MyST Markdown is a superset of Jupyter Markdown (AKA, CommonMark), " Hey Jupyter guys, can you please support asciidoc instead of inventing another MD format.
Sorry only 24h per day. Most of the work is volunteer. If you want ascii doc you'll need to put some elbow grease.
you will save the effort needed to maintain a new format.
Re: The new Jupyter Book
#46This is a really good move. A lot of people have been offering Jupyter Notebooks along with their Books. This should bring down the effort in getting the book out. An important note though, R world has for something called 'bookdown' for quite sometime and many R developers have used it to write books. https://bookdown.org/ The only worry is that now a lot of data science enthusiasts are going to try to publish their…
I'm personally a huge fan of `mdbook`, which seems to be the Rust equivalent of R's `bookdown`. I've switched out internal documentation over to it from `gitbook`. https://github.com/rust-lang/mdBook
For things that will be online only mdBook is great.
I'm currently testing honkit which is a gitbook-cli fork and it seems OK.
Re: The new Jupyter Book
#47Earlier 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.
My main concern with jupyter is that I prefer orgmode (and by a lot), but I know that it's niche and most people don't even heard about it ipnbs are preferred form of notebook exchange.
I will check how good translation to/from orgmode is then.
Re: The new Jupyter Book
#48I don't think there's a better stack in all of scientific computing than Julia + Jupyter Books. Lovin' it.
Julia + Pluto will probably give it a run for the money.
Re: The new Jupyter Book
#49I love the Jupyter ecosystem but it's frustratingly messy sometimes. There's already "nbconvert" built in to Jupyter (lab), built on Pandoc. It's extremely under-documented but it's possible to extend it with templates to generate arbitrary outputs. I've done this to directly generate branded PDF reports via latex. Jupyter Book has a lot of overlap with this feature, but rather than building on nbconvert/pandoc, it s…
>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?
https://codeocean.com/capsule/9155944/tree/v1
The nbconvert syntax is
jupyter nbconvert --exec --to latex --template ieee.tplx --output ../results/editorial.tex editorial.ipynb
and then `pdflatex` converts the tex file to a PDFRe: The new Jupyter Book
#50small 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.