# Ipyflow: an IPython kernel that keeps track of execution state

**URL:** <https://forum.access-hive.org.au/t/ipyflow-an-ipython-kernel-that-keeps-track-of-execution-state/396>\
**Category:** Technical\
**Tags:** python, jupyter\
**Created:** [6 February 2023 08:05 UTC](https://forum.access-hive.org.au/t/ipyflow-an-ipython-kernel-that-keeps-track-of-execution-state/396 "2023-02-06T08:05:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dougiesquire](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/dougiesquire/32/16_2.png) [@dougiesquire](https://forum.access-hive.org.au/u/dougiesquire)\
**Post date:** [6 February 2023 08:05 UTC](https://forum.access-hive.org.au/t/ipyflow-an-ipython-kernel-that-keeps-track-of-execution-state/396/1 "2023-02-06T08:05:34Z")

</div>

Just stumbled across this. ipyflow is an IPython kernel that keeps track of execution state and will flag or update dependent cells when an upstream change is made. There’re some good example videos in their [README](https://github.com/ipyflow/ipyflow).

---

<div class="post-metadata">

**Author:** ![navidcy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.access-hive.org.au/navidcy/32/101_2.png) [@navidcy](https://forum.access-hive.org.au/u/navidcy)\
**Post date:** [20 May 2023 05:54 UTC](https://forum.access-hive.org.au/t/ipyflow-an-ipython-kernel-that-keeps-track-of-execution-state/396/2 "2023-05-20T05:54:32Z")

</div>

This is nice!

I like reactive notebooks. They “force” you to write cleaner code and be less sloppy.

On a normal notebook often we run a cell and then add a cell above that knows a variable that has been defined below and it works when we run it but then if we forget to clean up this and give the notebook to somebody else they can’t run it. That happens a lot! A reactive notebook doesn’t suffer from this issue.

(Have a look here also [https://plutojl.org](https://plutojl.org))