The actions framework introduced a ReadOnlyError, and first included it in lume-impact.
When this is upstreamed to lume-base, the error was copied there, and the actions code referenced that exception. This means that notebooks that reference the impact ReadOnlyError will fail (it's a different exception, even though it shares the same name)
In particular: https://github.com/ChristopherMayes/lume-impact/blob/master/docs/examples/lume_model_tutorial.ipynb
This will break things once lume-base gets tagged with the actions code (>0.4.4)
The actions framework introduced a
ReadOnlyError, and first included it in lume-impact.When this is upstreamed to lume-base, the error was copied there, and the actions code referenced that exception. This means that notebooks that reference the impact
ReadOnlyErrorwill fail (it's a different exception, even though it shares the same name)In particular: https://github.com/ChristopherMayes/lume-impact/blob/master/docs/examples/lume_model_tutorial.ipynb
This will break things once lume-base gets tagged with the actions code (>0.4.4)