Use UV_INDEX_URL instead of UV_DEFAULT_INDEX

[nojaf]

Hello,

I was wondering if

marimo-lsp/extension/src/services/Uv.ts

Line 374 in 7ca6754

UV_DEFAULT_INDEX: "https://pypi.org/simple/",

could be refactored to use UV_INDEX_URL.

The current approach is not working for us in our airgapped environment.
We rely on UV_INDEX_URL to redirect to our internal Python repository.

Happy to send a PR if I'm making sense.

[mscolnick]

UV_INDEX_URL is actually deprecated, but there is an open PR out for better bootstrapping your ty and ruff environment

[nojaf]

Hi! Thanks for the work on PR #414 — the custom binary path support is a great addition.

However, I don't think it fully addresses the airgapped use case described in this issue. Even with PR #414, the uv pip install fallback path still bypasses any existing uv configuration:

1. UV_NO_CONFIG=1 (

   marimo-lsp/extension/src/services/Uv.ts

   Line 370 in 7ca6754

   UV_NO_CONFIG: "1",

   ) disables all uv configuration files, so our /etc/uv/uv.toml is completely ignored.
2. UV_DEFAULT_INDEX (

   marimo-lsp/extension/src/services/Uv.ts

   Line 372 in 7ca6754

   // otherwise it will fail when the user has a different python version installed.

   ) hardcodes https://pypi.org/simple/, overriding any user-configured index.

We have a system-wide /etc/uv/uv.toml that points uv at our internal registry:

  index-url = "https://our.domain.internal/api/pypi/pypi-all/simple"
  python-install-mirror = "https://our.domain.internal/generic-github-remote/astral-sh/python-build-standalone/releases/download"
  native-tls = true

Would it make sense to remove UV_NO_CONFIG=1 and the hardcoded UV_DEFAULT_INDEX so that the extension respects existing uv configuration? That would be enough to make things work for us out of the box. Happy to send a PR if that sounds like a reasonable approach!

[manzt]

With #414 (merged), for airgapped environments our recommendation is to install the charliermarsh.ruff and astral-sh.ty companion extensions — the marimo extension discovers their bundled binaries automatically and uv pip install never runs. Or set marimo.ruff.path / marimo.ty.path to point at locally-installed binaries.

More broadly, the rest of our uv integration (e.g., auto-installing packages for users) should defer to uv's own environment discovery.