-
-
Notifications
You must be signed in to change notification settings - Fork 173
Open
Description
When installing dependencies with uv, it identifies inconsistencies in requirements:
mlx-vlm % uv sync
× No solution found when resolving dependencies for split (markers: python_full_version == '3.9.*'):
╰─▶ Because the requested Python version (>=3.8) does not satisfy Python>=3.10 and gradio>=5.19.0 depends on Python>=3.10, we can conclude that gradio>=5.19.0 cannot be used.
And because only the following versions of gradio are available:
gradio<=5.19.0
gradio==5.20.0
gradio==5.20.1
gradio==5.21.0
gradio==5.22.0
gradio==5.23.0
gradio==5.23.1
gradio==5.23.2
gradio==5.23.3
gradio==5.24.0
gradio==5.25.0
gradio==5.25.1
gradio==5.25.2
gradio==5.26.0
gradio==5.27.0
gradio==5.27.1
gradio==5.28.0
gradio==5.29.0
gradio==5.29.1
gradio==5.30.0
gradio==5.31.0
gradio==5.32.0
gradio==5.32.1
gradio==5.33.0
gradio==5.33.1
gradio==5.33.2
gradio==5.34.0
gradio==5.34.1
gradio==5.34.2
gradio==5.35.0
gradio==5.36.2
gradio==5.37.0
gradio==5.38.0
gradio==5.38.1
gradio==5.38.2
gradio==5.39.0
gradio==5.40.0
gradio==5.41.0
gradio==5.41.1
gradio==5.42.0
gradio==5.43.0
gradio==5.43.1
gradio==5.44.0
gradio==5.44.1
we can conclude that gradio>=5.19.0 cannot be used.
And because mlx-vlm[ui] depends on gradio>=5.19.0 and your project requires mlx-vlm[ui], we can conclude that your project's requirements are unsatisfiable.
hint: The `requires-python` value (>=3.8) includes Python versions that are not supported by your dependencies (e.g., gradio>=5.19.0 only supports >=3.10). Consider using
a more restrictive `requires-python` value (like >=3.10).
hint: While the active Python version is 3.12, the resolution failed for other Python versions supported by your project. Consider limiting your project's supported Python
versions using `requires-python`.
Resolving them requires requiring Python 3.10 in pyproject.toml
which, altogether, seems a very sane requirement.
Metadata
Metadata
Assignees
Labels
No labels