From 8a1abebaaefb76c074c44b4612f06bd92e89ef32 Mon Sep 17 00:00:00 2001
From: AbsoluteVacuum <32832158+AbsoluteVacuum@users.noreply.github.com>
Date: Mon, 28 Sep 2026 13:09:40 +0300
Subject: [PATCH] added references to IPyflow and Marimo
---
scicomp/jupyter-pitfalls.rst | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/scicomp/jupyter-pitfalls.rst b/scicomp/jupyter-pitfalls.rst
index efa7c957d..88a247045 100644
--- a/scicomp/jupyter-pitfalls.rst
+++ b/scicomp/jupyter-pitfalls.rst
@@ -98,6 +98,10 @@ Solutions:
- But just like with modularity above, a notebook designed to be
easily testable isn't designed for interactive work.
+- However, if the notebooks are actually Python files like
+ `Marimo notebooks `__, they can easily be tested
+ `with Pytest `__ just
+ like regular Python.
- Transition to modules instead of testing in the notebook.
@@ -118,9 +122,10 @@ Solutions:
merging, VCS integration
- Jupyter `lab `__ /
notebook git integration work well.
-- Notebooks in other plain-text formats: Rmarkdown, `Jupytext
+- Notebooks in other formats: Rmarkdown, `Jupytext
`__ (pair notebooks with plain
- text versions).
+ text versions), `Marimo `__ (notebooks are
+ regular Python files).
- Remember, blobs in version control is still better than nothing.
@@ -146,6 +151,12 @@ Solutions:
run all" defeats the purpose of that, so... balance it out.)
- Design for modularity and clean interfaces, even within a notebook.
Don't make a mess.
+- `IPyflow `__ - reactive kernel for
+ Jupyter notebooks that removes hidden state, introduces cell dependencies,
+ and enables computation propagation (cascading updates on cell update).
+- `Marimo `__ - alternative to Jupyter with cell graph,
+ reactivity, custom web-based GUI like Jupyter Lab, and built-in package
+ management.