[X] I searched open reports and couldn't find a duplicate
What happened?
.tar.gz sdist are found instead of .whl when manylinux wheel are more recent than 2_17. This can cause long compilation on the machine doing conda-lock install. I believe https://github.com/conda/conda-lock/issues/395 has exactly the same root cause since the .whl in this case is a 2_27 and is not found by conda-lock and there is no sdist available on PyPI for open3d.
It is a bit tricky to know which manylinux wheels should be supported, since the ones supported by the machine running conda-lock lock are not necessarily supported by the machine running conda-lock install. Maybe some heuristics could be used like all the manylinux wheels until the most recent docker image supported by manylinux? Right now it is 2_28 according to https://github.com/pypa/manylinux/blob/main/README.rst#docker-images.
Conda Info
active environment : conda-lock
active env location : /home/lesteve/micromamba/envs/conda-lock
shell level : 1
user config file : /home/lesteve/.condarc
populated config files : /home/lesteve/dev/dotfiles/.condarc
conda version : 23.7.2
conda-build version : not installed
python version : 3.11.4.final.0
virtual packages : __archspec=1=x86_64
__glibc=2.38=0
__linux=6.5.3=0
__unix=0=0
base environment : /home/lesteve/micromamba (writable)
conda av data dir : /home/lesteve/micromamba/etc/conda
conda av metadata url : None
channel URLs : https://conda.anaconda.org/conda-forge/linux-64
https://conda.anaconda.org/conda-forge/noarch
package cache : /home/lesteve/micromamba/pkgs
/home/lesteve/.conda/pkgs
envs directories : /home/lesteve/micromamba/envs
/home/lesteve/.conda/envs
platform : linux-64
user-agent : conda/23.7.2 requests/2.31.0 CPython/3.11.4 Linux/6.5.3-arch1-1 endeavouros/rolling glibc/2.38
UID:GID : 1000:1000
netrc file : None
offline mode : False
Checklist
What happened?
.tar.gzsdist are found instead of.whlwhen manylinux wheel are more recent than2_17. This can cause long compilation on the machine doingconda-lock install. I believe https://github.com/conda/conda-lock/issues/395 has exactly the same root cause since the .whl in this case is a 2_27 and is not found by conda-lock and there is no sdist available on PyPI for open3d.To reproduce:
The lockfile has a sdist
.tar.gzrather than a.whl.lightgm has some manylinux_2_28 wheels that I can install fine on my Linux machine with pip: https://pypi.org/project/lightgbm/4.1.0/#files
I think this comes from the fact that the possible manylinux wheels recognised by conda-lock are hard-coded here (up until 2_17): https://github.com/conda/conda-lock/blob/f64b74ec91c57218bd11692b8e5cda3611d64649/conda_lock/pypi_solver.py#L42
It is a bit tricky to know which manylinux wheels should be supported, since the ones supported by the machine running
conda-lock lockare not necessarily supported by the machine runningconda-lock install. Maybe some heuristics could be used like all the manylinux wheels until the most recent docker image supported by manylinux? Right now it is 2_28 according to https://github.com/pypa/manylinux/blob/main/README.rst#docker-images.Conda Info
Conda Config
Conda list
Additional Context
No response