Package management¶
marimo supports package management for pip, rye, uv, poetry, pixi. When marimo comes across a module that is not installed, you will be prompted to install it using your preferred package manager.
Once the module is installed, all cells that depend on the module will be rerun.
Package Installation
We use some heuristic for guessing the package name in your registry (e.g. PyPI) from the module name. It is possible that the package name is different from the module name. If you encounter an error, please file an issue or help us by adding your mapping directly to the codebase.
Running marimo in a sandbox environment (uv only)¶
If you want to run marimo in a sandbox environment, you can use the --sandbox flag. This will create an isolated virtual environment (using uv) and install any packages listed in the script metadata, per PEP 723. If there is no package metadata in the script, marimo will still prompt you to install any missing packages.
This is useful when you want to run marimo in a clean environment without affecting your global environment.
Auto-tracking inline script metadata¶
When running with --sandbox, marimo will automatically track the package name metadata in your notebook file, per PEP 723. This metadata is used to manage the notebook's dependencies and Python version.
For example, whenever you add or remove a package, marimo will automatically update the script metadata in your notebook file:
# /// script
# requires-python = ">=3.11"
# dependencies = [
# "pandas==<version>",
# "altair==<version>",
# ]
# ///
This means your notebook file is a completely self-contained artifact with all the necessary information to run.
Sandbox creation configuration¶
Running marimo in a sandbox environment uses uv to create a virtual environment. You can use any of uv's supported environment variables.
Choosing the Python version¶
For example, you can specify the Python version using the UV_PYTHON environment variable:
Other common configuration¶
or you can use uv's link mode: