should --sandbox with uv require manually reinstalling ...

At a glance

The community member is experiencing a ModuleNotFound error and missing package issues when running marimo edit --sandbox and installing packages with uv. The packages are added to the top of the script, but the issues persist across notebook restarts. Another community member suggests this should not be expected behavior and may be a bug or edge case. They inquire about the versions of marimo and uv being used, and ask the original poster to list the package metadata at the top of the file. The versions provided indicate they are all up-to-date, but the issue remains unresolved.

ggabriel

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

5 comments

MMyles Scolnick

It should not be. Sounds like a bug or edge case? What version of marimo and uv? Can you list what’s at the top of the file?

ggabriel

Plain Text

# /// script
# requires-python = ">=3.11"
# dependencies = [
#     "marimo",
#     "openai==1.52.2",
#     "pydantic==2.9.2",
# ]
# ///

import marimo

__generated_with = "0.9.14"
app = marimo.App()

ggabriel

Plain Text

$ uv --version
uv 0.4.26

Get help from the marimo community

should --sandbox with uv require manually reinstalling packages each time Marimo is restarted?