pip install fails

[qlyoung]

Reproduction

1. Make a clean venv: mkdir vfs && cd vfs && python3 -m venv . && ./bin/activate
2. pip install vectorvfs

(vfs) qlyoung@aquila ~/vfs> pip install vectorvfs
Collecting vectorvfs
  Using cached vectorvfs-0.3.0-py3-none-any.whl.metadata (2.2 kB)
Collecting click>=8.1.8 (from vectorvfs)
  Using cached click-8.1.8-py3-none-any.whl.metadata (2.3 kB)
Collecting perception-models-perone>=1.0.0 (from vectorvfs)
  Using cached perception_models_perone-1.0.0-py3-none-any.whl.metadata (1.6 kB)
Collecting pillow>=11.0.0 (from vectorvfs)
  Using cached pillow-11.2.1-cp313-cp313-manylinux_2_28_x86_64.whl.metadata (8.9 kB)
Collecting rich>=14.0.0 (from vectorvfs)
  Using cached rich-14.0.0-py3-none-any.whl.metadata (18 kB)
Collecting torch==2.5.1 (from vectorvfs)
  Using cached torch-2.5.1-cp313-cp313-manylinux1_x86_64.whl.metadata (28 kB)
INFO: pip is looking at multiple versions of vectorvfs to determine which version is compatible with other requirements. This could take a while.
Collecting vectorvfs
  Using cached vectorvfs-0.1.0-py3-none-any.whl.metadata (2.1 kB)
ERROR: Cannot install vectorvfs==0.1.0 and vectorvfs==0.3.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    vectorvfs 0.3.0 depends on torchaudio==2.5.1
    vectorvfs 0.1.0 depends on perception-models

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Info

(vfs) qlyoung@aquila ~/vfs > python3 --version
Python 3.13.3

[perone]

This is new to me, can you try to recreate the environment and run pip install -U pip first and then pip install -U vectorvfs ? It looks like there is an issue with the environment to me.

[schmurian]

Same for me

[qlyoung]

It looks like there is an issue with the environment to me.

The environment was completely vanilla.

can you try to recreate the environment and run pip install -U pip first and then pip install -U vectorvfs?

https://ascii.qlyoung.net/a/2BQdfMy0NM1xpjcZg2I5Gloiz

[schmurian]

I created a venv with uv and python 3.12.8 on Linux Debian.

After that I ran uv pip install -U pip and pip install -U vectorvfs, which had the following output:

Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting vectorvfs
  Using cached vectorvfs-0.3.0-py3-none-any.whl.metadata (2.2 kB)
Collecting click>=8.1.8 (from vectorvfs)
  Using cached click-8.2.1-py3-none-any.whl.metadata (2.5 kB)
Collecting perception-models-perone>=1.0.0 (from vectorvfs)
  Using cached perception_models_perone-1.0.0-py3-none-any.whl.metadata (1.6 kB)
Collecting pillow>=11.0.0 (from vectorvfs)
  Downloading pillow-11.2.1-cp312-cp312-manylinux_2_28_aarch64.whl.metadata (8.9 kB)
Collecting rich>=14.0.0 (from vectorvfs)
  Using cached https://www.piwheels.org/simple/rich/rich-14.0.0-py3-none-any.whl (243 kB)
Collecting torch==2.5.1 (from vectorvfs)
  Downloading torch-2.5.1-cp312-cp312-manylinux2014_aarch64.whl.metadata (28 kB)
Collecting torchaudio==2.5.1 (from vectorvfs)
  Downloading torchaudio-2.5.1-cp312-cp312-manylinux2014_aarch64.whl.metadata (6.4 kB)
INFO: pip is looking at multiple versions of vectorvfs to determine which version is compatible with other requirements. This could
take a while.
Collecting vectorvfs
  Using cached vectorvfs-0.1.0-py3-none-any.whl.metadata (2.1 kB)
ERROR: Cannot install vectorvfs==0.1.0 and vectorvfs==0.3.0 because these package versions have conflicting dependencies.
The conflict is caused by:
    vectorvfs 0.3.0 depends on torchcodec==0.1
    vectorvfs 0.1.0 depends on perception-models
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict
ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts