-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guide "Using uv with marimo" #3075
base: main
Are you sure you want to change the base?
Changes from 14 commits
4d89817
d0e7dcc
a898848
47269a8
9c492f5
7e63d33
3a7a71c
f75303c
9a220a2
edde7cc
9cf9aa2
ae3f426
51c2b95
dd9c85f
9896b58
3d16d16
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,6 +6,7 @@ | |
:hidden: | ||
|
||
overview | ||
installation_uv | ||
reactivity | ||
interactivity | ||
outputs | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,260 @@ | ||
|
||
# Running Marimo with `uv` | ||
|
||
You can run a Marimo notebook using the package manager `uv` through one of the following methods: | ||
|
||
1. **Within a project environment** | ||
2. **Temporary installation (cached)** | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. maybe a "ephemeral virtual enviroment" There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree, I think "Ephemeral" is not widely recognized, especially by non-native English speakers. But I would also love to find a better word for |
||
3. **Directly from a URL** | ||
4. **Globally Installed Tool** | ||
|
||
--- | ||
|
||
## Running in a Project Environment | ||
|
||
We recommend running Marimo within a project-specific environment. | ||
Here's how you can set it up: | ||
|
||
```bash | ||
uv venv | ||
uv pip install marimo | ||
uv run marimo edit hi.py | ||
``` | ||
|
||
The `uv run` command provides the simplest way to access the virtual environment. | ||
|
||
However, if you prefer to activate it manually, you can do so with the following commands: | ||
|
||
```bash | ||
source .venv/bin/activate | ||
marimo edit hi.py | ||
``` | ||
|
||
--- | ||
### Using Specific Python Versions | ||
|
||
To specify a Python version, add the `--python` option while creating the venv. For example: | ||
|
||
```bash | ||
uv venv --python 3.13 | ||
``` | ||
|
||
```{admonition} Tip | ||
:class: tip | ||
|
||
uv will automatically fetch Python versions as needed — you don't need to install Python to get started. | ||
``` | ||
<!-- Source: https://docs.astral.sh/uv/guides/install-python/#installing-python --> | ||
|
||
|
||
If no version is specified, the default Python version is used (currently: **[TODO: Specify default Python version]**). | ||
|
||
--- | ||
|
||
### Installing Packages | ||
|
||
There are three ways to install additional packages: | ||
|
||
1. **Via Terminal** | ||
Run the following command: | ||
```bash | ||
uv pip install matplotlib polars | ||
``` | ||
|
||
2. **Within the Notebook** | ||
Type `import polars as pd`. Run the cell, and a "Missing package" pop up window will appear. | ||
|
||
<div align="center"> | ||
<figure> | ||
<img src="/_static/image.png" width="650px"/> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can we rename these images to be more descriptive |
||
<figcaption> | ||
Screenshot demonstrating the "Missing package" window. | ||
</figcaption> | ||
</figure> | ||
</div> | ||
|
||
|
||
3. **Using the Packages Tab** | ||
Navigate to the "Packages" tab and select the desired package. | ||
|
||
<div align="center"> | ||
<figure> | ||
<img src="/_static/image-1.png" width="400px"/> | ||
<figcaption> | ||
Screenshot demonstrating the "Packages" tab. | ||
</figcaption> | ||
</figure> | ||
</div> | ||
|
||
|
||
### Defining Dependencies with `pyproject.toml` | ||
|
||
A pyproject.toml file makes it easier to manage your project’s dependencies in one place. Using `uv`, you can quickly set up and customize your project’s environment | ||
|
||
```bash | ||
uv init # Creates a pyproject.toml file | ||
uv add marimo # Adds "marimo>=0.9.31" to dependencies | ||
uv run marimo edit hi.py | ||
``` | ||
|
||
|
||
### Reading a `pyproject.toml` from an Existing Project | ||
|
||
If you already have a `pyproject.toml` file—for example, when cloning an existing project—you can use the `uv sync` command to synchronize and install the dependencies defined within it: | ||
|
||
```bash | ||
uv sync | ||
uv run marimo edit hi.py | ||
|
||
``` | ||
|
||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. not sure what IDE you are using, but most of markdown plugins that will autoformat your markdown. it would be useful to install to avoid PR comments about it There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point! I use the "Prettier" Markdown formatter and will re-format the code. |
||
|
||
This command ensures that your environment matches the dependency specifications of the existing project, making it simple to get up and running without manually adding packages. | ||
|
||
|
||
## Temporary Installation | ||
|
||
When you execute a command using `uv tool run`, no virtual environment folder is created in your working directory. Instead, `uv` takes the following steps: | ||
|
||
1. **Caches dependencies or reuses existing cached ones** based on the metadata in the Marimo notebook. | ||
2. **Creates a temporary virtual environment** on your system. | ||
3. **Deletes the temporary environment** immediately after the process ends. | ||
|
||
This lightweight approach keeps your workspace clean while still providing an isolated, dependency-managed environment for running commands. | ||
|
||
For instance, you can run: | ||
|
||
```bash | ||
uv tool run marimo edit hi.py | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we should just always suggest using There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point! Maybe |
||
``` | ||
|
||
During the session, you can install additional packages, but their information will not be preserved once the session ends. This is where notebook metadata comes into play, as explained in the following section. | ||
|
||
--- | ||
|
||
### Specifying Additional Requirements | ||
|
||
|
||
#Todo: check how similar this is to https://docs.marimo.io/guides/editor_features/package_management.html#package-management | ||
|
||
To include dependency information to the metadata, use the --sandbox option: | ||
|
||
```bash | ||
uv tool run marimo edit hi.py --sandbox | ||
``` | ||
|
||
While working in the notebook, you can install packages through pop-ups or via the **Packages** tab. However, **adding packages through the terminal is not supported in sandbox mode.** *(#TODO: Fact-check this limitation.)* | ||
|
||
--- | ||
|
||
### Fully Self-Contained Notebooks | ||
|
||
A unique feature of this setup is that the notebook becomes **fully self-contained** and reproducible by anyone. This is achieved by embedding package metadata directly within the notebook, following the guidelines of [PEP 723 – Inline Script Metadata](https://peps.python.org/pep-0723/). | ||
|
||
When opened in a plain text editor, the notebook displays the following embedded metadata: *(#TODO: Replace this example with a screenshot from a text editor. and add a green circle around the metadata)* | ||
|
||
```python | ||
# /// script | ||
# requires-python = ">=3.11" | ||
# dependencies = [ | ||
# "polars==1.16.0", | ||
# ] | ||
# /// | ||
|
||
import marimo | ||
|
||
__generated_with = "0.9.31" | ||
app = marimo.App(width="medium") | ||
|
||
|
||
@app.cell | ||
def __(): | ||
import polars | ||
return (polars,) | ||
``` | ||
|
||
Once the session ends, the venv is cleared. | ||
To reconstruct the session, simply run: | ||
|
||
```bash | ||
uv tool run marimo edit hi.py --sandbox | ||
``` | ||
|
||
Marimo detects the embedded dependencies in sandbox mode, so you can also use: | ||
|
||
```bash | ||
uv tool run marimo edit hi.py | ||
``` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. you can delete this part, its not too informational / adds confusion
|
||
|
||
In this case, the Marimo CLI will show: | ||
|
||
```bash | ||
Run in a sandboxed venv containing this notebook's dependencies? | ||
[Y/n] | ||
``` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same as here, we don't need to explain this |
||
|
||
--- | ||
|
||
### Simplifying with `uvx` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this doc should be a tool about using uv with marimo and less about a i would:
this could be simply, There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. good point! |
||
|
||
For convenience, `uvx` is a shorthand for `uv tool run`. These two commands are equivalent: | ||
|
||
```bash | ||
uv tool run marimo edit hi.py | ||
uvx marimo edit hi.py | ||
``` | ||
## From URL | ||
|
||
This pattern will run marimo from a URL. | ||
|
||
``` | ||
uvx marimo edit --sandbox https://gist.githubusercontent.com/kolibril13/a59135dd0973b97d488ba21c650667fe/raw/5f98021b5d3c024d5827fa9464787517495178b4/marimo_minimal_numpy_example.py | ||
``` | ||
|
||
#TODO One sentence about portability. | ||
|
||
**Note:** | ||
1. This command will run code from a URL. Make sure you trust the source before proceeding. | ||
2. Upon execution, you’ll be prompted: | ||
``` | ||
Would you like to run it in a secure docker container? [Y/n]: | ||
``` | ||
To proceed securely, ensure you have [Docker](https://www.docker.com/) installed and running, then press `Y`. | ||
3. Include `.py` at the end of the filename *(#TODO: Fact-check if that's really the case)* | ||
|
||
# Globally Installed Tool | ||
|
||
It is generally **not recommended** to install tools globally, as dependencies will also be installed globally. *(#TODO: Fact-check this recommendation.)* | ||
|
||
### Installation | ||
|
||
To install the tool globally, use: | ||
|
||
```bash | ||
uv tool install marimo | ||
``` | ||
|
||
### Using a Specific Python Version | ||
|
||
To install the tool globally with a specific Python version, use the following command. This will overwrite any existing global installation: | ||
|
||
```bash | ||
UV_PYTHON=python3.11 uv tool install marimo | ||
``` | ||
|
||
### Updating the Global Version | ||
|
||
To update the global version of Marimo, run: | ||
|
||
```bash | ||
uv tool install marimo --upgrade | ||
``` | ||
|
||
### Uninstallation | ||
|
||
To uninstall the globally installed tool, use: | ||
|
||
```bash | ||
uv tool uninstall marimo | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
marimo
is lowercase everywhere as a library