Sorry I missed this! Discourse sometimes notifies me of new posts and sometimes decides not to. If I’d seen it I would have got back to you quicker.
Yeah, it’s hard to get the right work flow! Text (rst) files are much easier to work with when you have a big batch of them. But notebooks are executable, so you need them to test your code.
For that reason, we’ve been working on a new tool, which we’ve called Jupinx, that takes a Sphinx project with a bunch of rst files and builds a set of corresponding notebooks. It does it in an intelligent way, so that only rst files that have been edited since the last build are recreated. As a result it’s pretty fast.
The work flow is then to work with the rst files, re-build notebooks, test code, work more with rst files, repeat.
It’s kind of like the edit tex file -> latex builder -> view pdf -> edit tex file workflow.
We’re about to release Jupinx as an open source project. @mamckay Would you mind to update Jonathan on the status of the project? Jonathan, we’d appreciate any feedback if you do give it a go.