Tight pins in conda package for 0.44.0rc1

[hoxbro]

Reporting a bug

Trying to test out numba rc 0.61.0rc1, I have noticed tight pins on zlib and libxml2.

An example of this is that this will not be solved:

 conda create -n tmp "python=3.13" "numba::llvmlite=0.44.0rc1" -c numba -c conda-forge

Channels:
 - numba
 - conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): done
Solving environment: failed

LibMambaUnsatisfiableError: Encountered problems while solving:
  - nothing provides _python_rc needed by python-3.13.0rc1-h3b4618f_0_cp313t

Could not solve for environment specs
The following packages are incompatible
├─ llvmlite 0.44.0rc1*  is installable with the potential options
│  ├─ llvmlite 0.44.0rc1 would require
│  │  └─ python >=3.10,<3.11.0a0 , which can be installed;
│  ├─ llvmlite 0.44.0rc1 would require
│  │  └─ python >=3.11,<3.12.0a0 , which can be installed;
│  ├─ llvmlite 0.44.0rc1 would require
│  │  └─ python >=3.12,<3.13.0a0 , which can be installed;
│  └─ llvmlite 0.44.0rc1 would require
│     ├─ python >=3.13,<3.14.0a0 , which requires
│     │  └─ libzlib >=1.3.1,<2.0a0  with the potential options
│     │     ├─ libzlib 1.3.1 would require
│     │     │  └─ zlib 1.3.1 *_1, which can be installed;
│     │     ├─ libzlib 1.3.1 would require
│     │     │  └─ zlib 1.3.1 *_2, which can be installed;
│     │     └─ libzlib 1.3.1 would require
│     │        └─ zlib 1.3.1 *_0, which can be installed;
│     └─ zlib >=1.2.13,<1.3.0a0 , which conflicts with any installable versions previously reported;
└─ python 3.13**  is not installable because there are no viable options
   ├─ python 3.13.0, which cannot be installed (as previously explained);
   └─ python [3.13.0rc1|3.13.0rc2|3.13.0rc3] would require
      └─ _python_rc, which does not exist (perhaps a missing channel).

On Windows, the libxml2 pin also causes problems (I don't have an MRE for this one).

Looking at the recipes for some of the builds of the RC, I can see they have tight pins that are not there in the template recipe:

llvmlite/conda-recipes/llvmlite/meta.yaml

Lines 40 to 46 in e9f12c6

	run:
	- python >=3.10
	- vs2015_runtime # [win]
	# osx has dynamically linked libstdc++
	- libcxx >=4.0.1 # [osx]
	- zlib
	- zstd

https://anaconda.org/numba/llvmlite/0.44.0rc1/download/linux-64/llvmlite-0.44.0rc1-py313h84b9e52_0.tar.bz2

  run:
    - libgcc-ng >=7.5.0
    - libstdcxx-ng >=7.5.0
    - python >=3.13,<3.14.0a0
    - python_abi 3.13.* *_cp313
    - zlib >=1.2.13,<1.3.0a0
    - zstd

https://anaconda.org/numba/llvmlite/0.44.0rc1/download/win-64/llvmlite-0.44.0rc1-py312h9a6739d_0.tar.bz2

  run:
    - libxml2 >=2.13.1,<2.14.0a0
    - python >=3.12,<3.13.0a0
    - vc >=14,<15.0a0
    - vc >=14.2,<15.0a0
    - vs2015_runtime >=14.29.30133,<15.0a0
    - zlib
    - zstd

• I have tried using the latest released version of llvmlite (most recent is
  visible in the change log (https://github.com/numba/llvmlite/blob/main/CHANGE_LOG).
• I have included a self contained code sample to reproduce the problem.
  i.e. it's possible to run as 'python bug.py'.

[NateNohling]

Is there an update on this? Cant seem to run python 3.13 with llvm/numba and pyarrow due to zlib.

[sklam]

For the conda-forge issue, it will be fixed by a conda-forge specific build: conda-forge/llvmlite-feedstock#95

The tight pinning on zlib and libxml2 are coming the anaconda-flavored build requirement upstream which we don't control.