## 📝 Summary

Fixes #5185. Changes the default package manager to `uv` when marimo is
launched from `uv` executable (e.g., `uv run marimo` in a project, or
`uvx marimo`). Expect behavior with this PR (without setting a package
manager):


```py
# prefers uv when launched from uv
uv init foo && cd foo
uv add marimo
uv run marimo edit test.py

# prefers pip when inside the environment
source .venv/bin/activate
marimo edit test.py
```

```py
# prefers uv when run with `uvx`
uvx marimo
```

We could probably try to be smarter in the case above where it defaults
to `pip` (since `uv` environments don't have `pip` installed), but I
think this is the safest and has the nice property of the `uvx marimo`
for the first time use case preferring uv.

## 🔍 Description of Changes

`uv run` and `uv tool run` (aka `uvx`) sets `UV` to the `uv` executable
path (astral-sh/uv#11326), which we inspect to
infer the preferred default package.

I think it's probably most safe to infer the "preferred" package manager
is `uv` when running from inside uv, so this bypasses the
`pyproject.toml` inspection.

## 📋 Checklist

- [x] I have read the [contributor
guidelines](https://github.com/marimo-team/marimo/blob/main/CONTRIBUTING.md).
- [x] For large changes, or changes that affect the public API: this
change was discussed or approved through an issue, on
[Discord](https://marimo.io/discord?ref=pr), or the community
[discussions](https://github.com/marimo-team/marimo/discussions) (Please
provide a link if applicable).
- [x] I have added tests for the changes made.
- [x] I have run the code and verified that it works as expected.

## 📜 Reviewers

@akshayka

…5213)

## 📝 Summary

Fixes marimo-team#5185. Changes the default package manager to `uv` when marimo is
launched from `uv` executable (e.g., `uv run marimo` in a project, or
`uvx marimo`). Expect behavior with this PR (without setting a package
manager):


```py
# prefers uv when launched from uv
uv init foo && cd foo
uv add marimo
uv run marimo edit test.py

# prefers pip when inside the environment
source .venv/bin/activate
marimo edit test.py
```

```py
# prefers uv when run with `uvx`
uvx marimo
```

We could probably try to be smarter in the case above where it defaults
to `pip` (since `uv` environments don't have `pip` installed), but I
think this is the safest and has the nice property of the `uvx marimo`
for the first time use case preferring uv.

## 🔍 Description of Changes

`uv run` and `uv tool run` (aka `uvx`) sets `UV` to the `uv` executable
path (astral-sh/uv#11326), which we inspect to
infer the preferred default package.

I think it's probably most safe to infer the "preferred" package manager
is `uv` when running from inside uv, so this bypasses the
`pyproject.toml` inspection.

## 📋 Checklist

- [x] I have read the [contributor
guidelines](https://github.com/marimo-team/marimo/blob/main/CONTRIBUTING.md).
- [x] For large changes, or changes that affect the public API: this
change was discussed or approved through an issue, on
[Discord](https://marimo.io/discord?ref=pr), or the community
[discussions](https://github.com/marimo-team/marimo/discussions) (Please
provide a link if applicable).
- [x] I have added tests for the changes made.
- [x] I have run the code and verified that it works as expected.

## 📜 Reviewers

@akshayka

…5213)

## 📝 Summary

Fixes marimo-team#5185. Changes the default package manager to `uv` when marimo is
launched from `uv` executable (e.g., `uv run marimo` in a project, or
`uvx marimo`). Expect behavior with this PR (without setting a package
manager):


```py
# prefers uv when launched from uv
uv init foo && cd foo
uv add marimo
uv run marimo edit test.py

# prefers pip when inside the environment
source .venv/bin/activate
marimo edit test.py
```

```py
# prefers uv when run with `uvx`
uvx marimo
```

We could probably try to be smarter in the case above where it defaults
to `pip` (since `uv` environments don't have `pip` installed), but I
think this is the safest and has the nice property of the `uvx marimo`
for the first time use case preferring uv.

## 🔍 Description of Changes

`uv run` and `uv tool run` (aka `uvx`) sets `UV` to the `uv` executable
path (astral-sh/uv#11326), which we inspect to
infer the preferred default package.

I think it's probably most safe to infer the "preferred" package manager
is `uv` when running from inside uv, so this bypasses the
`pyproject.toml` inspection.

## 📋 Checklist

- [x] I have read the [contributor
guidelines](https://github.com/marimo-team/marimo/blob/main/CONTRIBUTING.md).
- [x] For large changes, or changes that affect the public API: this
change was discussed or approved through an issue, on
[Discord](https://marimo.io/discord?ref=pr), or the community
[discussions](https://github.com/marimo-team/marimo/discussions) (Please
provide a link if applicable).
- [x] I have added tests for the changes made.
- [x] I have run the code and verified that it works as expected.

## 📜 Reviewers

@akshayka