From the logs that flash by as marimo starts in sandbox mode, it seems it installs the version of the marimo package from pypi that corresponds to the running version's version. This works fine with official releases, but makes it hard to test development branches, since they still have the prior version number, so the running notebook won't reflect the changes

I tried installing the dev branch of marimo that I wanted to try from within the notebook itself, but that didn't work either:

when running marimo edit --sandbox and installing packages with uv, i'm seeing a ModuleNotFound error and the missing packages pop-over each time the notebook is re-opened after marimo is restarted. is that expected? or should the packages be reinstalled automatically/persisted between runs?

FWIW the package metadata is added to the top of the script