Skip to content

docs: request the mlx extra in the documented setup commands - #2245

Open
mlpy0 wants to merge 1 commit into
exo-explore:mainfrom
mlpy0:mlx-extra-setup-docs
Open

docs: request the mlx extra in the documented setup commands#2245
mlpy0 wants to merge 1 commit into
exo-explore:mainfrom
mlpy0:mlx-extra-setup-docs

Conversation

@mlpy0

@mlpy0 mlpy0 commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Since #2087 moved mlx, mlx-lm, mlx-vlm and mflux out of dependencies into the mlx extra, the documented setup path never installs them, and [tool.uv] sets no default extras. uv run exo starts the API, then every runner crashes with ModuleNotFoundError: No module named 'mlx' (#2156).

Adds the extra to the commands documented as the way to set up:

  • README macOS: uv sync --extra mlx
  • README Linux: uv sync --extra mlx-cpu, with the mlx-cuda12 / mlx-cuda13 alternatives
  • CONTRIBUTING.md quick start
  • just sync / just sync-clean, which just build-app runs before pyinstaller — the spec aborts when the mlx Metal libraries are missing

Docs plus two justfile recipes; no dependency or lock changes. Backend choice stays explicit, since mlx-cpu / mlx-cuda12 / mlx-cuda13 / mlx-none are declared as conflicting extras.

#2234 overlaps on the macOS README block only, via a setup script that runs uv sync --extra mlx; the Linux block, CONTRIBUTING.md and the justfile are not covered there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant