From 9b2db69d28211891482fcb274c0a8439b513f1c0 Mon Sep 17 00:00:00 2001 From: RyanOnTheInside <7623207+ryanontheinside@users.noreply.github.com> Date: Thu, 19 Feb 2026 18:22:56 -0500 Subject: [PATCH] fix: remove --torch-backend from plugin dependency compilation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The compile step (_compile_plugins) resolves compatible package versions, while the install step (_sync_plugins) fetches platform-specific builds. Passing --torch-backend cu128 during compilation conflates these concerns — it forces the resolver to use the cu128 index for all torch ecosystem packages, even those that lack wheels on that index for the current platform (e.g. torchao 0.15.0+cu128 has no Windows wheels). Without this flag, the compile step resolves versions from PyPI where torchao is available as a platform-independent wheel (py3-none-any). The install step still uses --torch-backend cu128 to fetch the correct CUDA builds for torch and torchvision. This works because local version tags (+cu128) only affect which binary is downloaded, not version resolution or dependency metadata. Signed-off-by: RyanOnTheInside <7623207+ryanontheinside@users.noreply.github.com> --- src/scope/core/plugins/manager.py | 1 - 1 file changed, 1 deletion(-) diff --git a/src/scope/core/plugins/manager.py b/src/scope/core/plugins/manager.py index 5605893f..e461a8ad 100644 --- a/src/scope/core/plugins/manager.py +++ b/src/scope/core/plugins/manager.py @@ -221,7 +221,6 @@ def _compile_plugins( "pip", "compile", str(pyproject), - *_get_torch_backend_args(), "-o", str(resolved_file), ]