pixi icon indicating copy to clipboard operation
pixi copied to clipboard

PyPI dependencies that will not install

Open tdejager opened this issue 1 year ago • 2 comments

I've upgraded this comment int a seperate issue so we can track it a bit easier.

Taken from issue: #771

--- Copy ----

@tdejager I wrote a simple script to test which PyPI packages cannot be managed by pixi. I have only tested a few packages I use. Here is the results from workflow run:

Results
Package pip pixi uv
confz
dvc
dvclive
icecream
jax
jax[cuda12]
matplotlib
meshio[all]
meshpy
meshtaichi-patcher
mkdocs
mkdocs-material
mkdocstrings[python]
numpy
pymeshfix
pyright
pytest
pytest-benchmark
pyvista
ruff
scipy
sparse
taichi
trimesh[all]
typeguard

I also noticed that pixi tends to build from source distributions rather than using built distributions. If the PyPI package does not provide source distributions, it cannot be installed (e.g. gmsh, jaxlib). I guess this is because pixi fails to resolve built distributions correctly.

Originally posted by @liblaf in https://github.com/prefix-dev/pixi/issues/771#issuecomment-2312340227

--- Copy ---

tdejager avatar Aug 27 '24 12:08 tdejager

I've just tested dvc and that seemed to work, any chance we could get some output to compare errors for those failures?

tdejager avatar Aug 27 '24 12:08 tdejager

We can download logs from workflow artifacts.

For sparse:

  • Dependencies resolved by pip are: sparse-0.15.4 <-- numba-0.60.0 <-- llvmlite-0.43.0
  • Dependencies resolved by pixi or uv are: sparse-0.15.4 <-- numba-0.51.2 <-- llvmlite-0.34.0
  • llvmlite-0.34.0 does not provide built distribution for python 3.12. Building llvmlite from source requires llvm installed, thus raising an error during installation.

liblaf avatar Aug 27 '24 13:08 liblaf

I think we are running a wheel test for most of these that should be succeeding now :)

tdejager avatar Jul 08 '25 08:07 tdejager