Unable to install vedo on WSL2 Windows on ARM

[darshansarojini]

I am running WSL2 on a Windows on ARM machine.
I have a conda environment with Python 3.10.15
Running the command pip install vedo gives the following error

ERROR: Cannot install vedo==2020.3.2, vedo==2020.3.3, vedo==2020.3.4, vedo==2020.4.0, vedo==2020.4.1, vedo==2020.4.2, vedo==2021.0.2, vedo==2021.0.3, vedo==2021.0.5, vedo==2021.0.6, vedo==2021.0.7, vedo==2022.0.1, vedo==2022.1.0, vedo==2022.2.0, vedo==2022.2.3, vedo==2022.3.0, vedo==2022.3.1, vedo==2022.4.1, vedo==2022.4.2, vedo==2023.4.3, vedo==2023.4.4, vedo==2023.4.5, vedo==2023.4.6, vedo==2023.4.7, vedo==2023.5.0, vedo==2024.5.1 and vedo==2024.5.2 because these package versions have conflicting dependencies.

The conflict is caused by:
vedo 2024.5.2 depends on vtk
vedo 2024.5.1 depends on vtk
vedo 2023.5.0 depends on vtk
vedo 2023.4.7 depends on vtk
vedo 2023.4.6 depends on vtk
vedo 2023.4.5 depends on vtk
vedo 2023.4.4 depends on vtk
vedo 2023.4.3 depends on vtk
vedo 2022.4.2 depends on vtk
vedo 2022.4.1 depends on vtk
vedo 2022.3.1 depends on vtk
vedo 2022.3.0 depends on vtk<9.1.0
vedo 2022.2.3 depends on vtk<9.1.0
vedo 2022.2.0 depends on vtk<9.1.0
vedo 2022.1.0 depends on vtk<9.1.0
vedo 2022.0.1 depends on vtk<9.1.0
vedo 2021.0.7 depends on vtk<9.1.0
vedo 2021.0.6 depends on vtk
vedo 2021.0.5 depends on vtk
vedo 2021.0.3 depends on vtk
vedo 2021.0.2 depends on vtk
vedo 2020.4.2 depends on vtk
vedo 2020.4.1 depends on vtk<9.0.0
vedo 2020.4.0 depends on vtk
vedo 2020.3.4 depends on vtk
vedo 2020.3.3 depends on vtk
vedo 2020.3.2 depends on vtk

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

[marcomusy]

this is very strange , have you tried installing vtk first?

[darshansarojini]

I tried installing vtk first, but unable to do so.

[marcomusy]

Sorry for the late reply - unfortunately this looks lilke a problem woith vtk, not vedo, it looks that there are no vtk python wheels for you hardware.

[darshansarojini]

Thank you. Yes, I need to request support for this issue with vtk.