jupytext VS mercury

Jupytext (https://github.com/mwouts/jupytext) has been designed exactly for this

jupytext is your friend.

So if you run your own jupyter server, -jupy+text can be a great workflow : it takes your notebook synchronized with other formats (python file, makdown, ...), so you can edit your py/md file with neovim, and refresh the browser to execute the notebook.

Automatically convert ipynb files to py when saving them on JupyterLab

I don't use Jupyter so I don't know for sure, but on a quick glance you might want to look at https://github.com/mwouts/jupytext to see if that could help at all.

The format is only partially invented, it follows Jupytext [0], but adds support for cell metadata. There is no obvious way to get that in fenced codeblocks, especially with the ability to spread it over multiple lines so it plays well with version control.

One more consideration is that it's not "Markdown with code blocks interspersed", one might as well use plaintext or AsciiDoc.

Of course there are tradeoffs.. I wish I had more time to work on it.

[0]: https://github.com/gzuidhof/starboard-notebook/blob/master/d...

[1]: https://github.com/mwouts/jupytext

Using jupytext (allows you to open .md files as notebooks) + jupyter gives you pretty much the same experience. The main issue is that the cell's output will be discarded. To fix it, you can use ploomber to generate an output HTML, so the workflow goes like this:

First, the format. The ipynb format does not play nicely with git since it stores the cell's source code and output in the same file. But Jupyter has built-in mechanisms to allow other formats to look like notebooks. For example, here's a library that allows you to store notebooks on a postgres database (I know this isn't practical, but it's a great example). To give more practical advice, jupytext allows you to open .py files as notebooks. So you can develop interactively but in the backend, you're storing .py files.

Web App is using two open-source packages that I've created:

- MLJAR AutoML - Python package for AutoML on tabular data https://github.com/mljar/mljar-supervised

- Mercury - framework for converting Jupyter Notebooks into Web App https://github.com/mljar/mercury

You can run Web App locally. What is more, you can adjust notebook's code for your needs. For example, you can set different validation strategies or evalutaion metrics or longer training times. The notebooks in the repo are good starting point for you to develop more advanced apps.

The GitHub repository https://github.com/mljar/mercury

We are working on open-source web framework Mercury that converts Python notebooks to Web Apps.

It is very opinionated:

- it has no callbacks - we automatically re-execute cells below updated widget

- it has no layout widgets, all input widgets are always in the left sidebar

Thanks to above decisions you don't need to change notebook's code to have web app and fit to the framework.

The simplicity of the framework is very important to us. We also care about deployment simplicity. That's why we created a shared hosting service called Mercury Cloud. You can deploy notebook by uploading a file.

The GitHub repository https://github.com/mljar/mercury

Documentation https://RunMercury.com/docs/

Mercury Cloud https://cloud.runmercury.com

Analysis was done in Jupyter Notebook with Python 3.10, Pandas, Matplotlib, wordcloud and Mercury framework.

Analysis was done in Jupyter Notebook with Python 3.10 kernel, Pandas, Matplotlib, wordcloud and Mercury framework to share notebook as a web application with widgets and code hidden. Gif created in Canva.

Mercury is a framework for converting Jupyter Notebooks to interactive apps (Voila killer),