uv lock / uv sync fails: unsatisfiable extras (and libreyolo[all] can't be installed on Python ≥ 3.12) #989

uv lock / uv sync fails: unsatisfiable extras (and libreyolo[all] can't be installed on Python ≥ 3.12)

Summary

On current dev (092ce18), uv can't resolve the project at all. Fixing the first error only exposes the next one. There are five separate causes in pyproject.toml. One of them also affects pip users: pip install "libreyolo[all]" can't succeed on Python ≥ 3.12.

Reproduce

uv lock --dry-run   # uv 0.11.8

Because libreyolo:dev depends on pytest>=9.0.2 and executorch==1.2.0 depends on pytest<9.0,
we can conclude that executorch==1.2.0 and libreyolo:dev are incompatible.
And because only the following versions of executorch are available:
    executorch<=1.2.0
    executorch>1.3
and libreyolo[executorch] depends on executorch>=1.2,<1.3 ...
your project's requirements are unsatisfiable.

Root causes

Each cause below was found by fixing the previous one and running the lock again.

Upgrading executorch doesn't help. Versions 1.3.1 and later drop the pytest pin but need torch>=2.12, and the pytorch-cu128 index stops at torch 2.11.

Proposed fix (tested: uv lock resolves)

 [dependency-groups]
 dev = [
-    "pytest>=9.0.2",
+    "pytest>=8.3",

 coreai = [
-    "coreai-torch>=0.4.1; sys_platform == 'darwin'",
+    "coreai-torch>=0.4.1; sys_platform == 'darwin' and python_version >= '3.11'",
 ]

 all = [
     ...
-    "libreyolo[paddle]",

(An alternative is to keep it as "libreyolo[paddle]; python_version < '3.12'".)

 [tool.uv]
 conflicts = [
     ...
+    [{ extra = "molmo2" }, { extra = "vla" }],
+    [{ extra = "marigold" }, { extra = "vla" }],
+    [{ extra = "paddle" }, { extra = "tflite" }],
+    [{ extra = "paddle" }, { extra = "litert" }],
+    [{ extra = "executorch" }, { extra = "tflite" }],
+    [{ extra = "executorch" }, { extra = "litert" }],
+    [{ extra = "executorch" }, { extra = "all" }],
 ]

With these changes the lock resolves executorch 1.2.0 with torch 2.11.0+cu128. pytest resolves to 8.4.2 alongside executorch and 9.0.2 alongside tflite.

Notes

• No test uses a pytest-9-only API (subtests, RaisesGroup, etc.), so lowering the dev floor looks safe.
• executorch and tflite/litert can't share an environment until executorch can move past 1.2 (blocked on a torch ≥ 2.12 CUDA index). Their tests have to run in separate environments.
• No uv.lock is committed and nothing in CI runs uv lock, so this drifted unnoticed. A uv lock --check (or uv lock --dry-run) step in CI would catch the next one.