Our recently introduced change to handle the demo notebook with Jupytext causes a run of the entire notebook on every change to the docs via the hot reloading of mkdocs serve.
Since the note book is rebuild everytime from jupytext, it is executed on every hot reload.
After some time of working on the docs, the notebook execution fails because the Open Meteo API blocks too many requests. Then one can not work on the docs.
Our recently introduced change to handle the demo notebook with Jupytext causes a run of the entire notebook on every change to the docs via the hot reloading of
mkdocs serve.Since the note book is rebuild everytime from jupytext, it is executed on every hot reload. After some time of working on the docs, the notebook execution fails because the Open Meteo API blocks too many requests. Then one can not work on the docs.
Alternatives to be considered: 1) https://jupyter-cache.readthedocs.io/en/latest/ OR 2) implement client side caching for API access.