From 13f79e4d6c5ee67634e73c0b428ab6f686913d0a Mon Sep 17 00:00:00 2001 From: Daniel Han Date: Thu, 7 May 2026 10:06:12 +0000 Subject: [PATCH] fix(install): pin click+shellingham in no-torch-runtime.txt install.sh / install.ps1 install no-torch-runtime.txt with --no-deps, which means typer's runtime dependencies (click, shellingham) never land. On Linux/Mac CI click happens to be cached transitively from previous jobs in the runner image; on a fresh windows-latest venv unsloth studio setup fails the very first time it runs: Traceback (most recent call last): File ".../unsloth/__main__.py", line 4, in from unsloth_cli import app File ".../unsloth_cli/__init__.py", line 4, in import typer File ".../typer/__init__.py", line 7, in from click.exceptions import Abort as Abort ModuleNotFoundError: No module named 'click' Pin click and shellingham explicitly so the no-torch path works on every fresh venv, on every OS. --- studio/backend/requirements/no-torch-runtime.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/studio/backend/requirements/no-torch-runtime.txt b/studio/backend/requirements/no-torch-runtime.txt index 3b822ac2a4..cbb5488deb 100644 --- a/studio/backend/requirements/no-torch-runtime.txt +++ b/studio/backend/requirements/no-torch-runtime.txt @@ -8,6 +8,13 @@ # unsloth direct deps (from pyproject.toml [project].dependencies) typer +# typer's runtime deps. Required explicitly because this file is +# installed with --no-deps. On Linux/Mac CI runners click is often +# already cached from previous jobs; on a fresh windows-latest venv +# it is not, and `unsloth studio setup` fails immediately with +# `ModuleNotFoundError: No module named 'click'`. +click>=8.0 +shellingham>=1.5 pydantic pyyaml nest-asyncio