Problem installing latest on Python 3.13 RC

[hoxbro]

Solution to issue cannot be found in the documentation.

• I checked the documentation.

Issue

I am trying to test packages with Python 3.13. Noticied that I could not install ipykernel and that it has the following pin: jupyter_core >=4.12,!=5.0.*, which currently is not possible to solve:

mamba create -n python313 python=3.13 "jupyter_core >=4.12,!=5.0.*" -c conda-forge/label/python_rc --dry-run

Looking for: ['python=3.13', "jupyter_core[version='>=4.12,!=5.0.*']"]

conda-forge/linux-64                                        Using cache
conda-forge/noarch                                          Using cache
conda-forge/label/python_rc/noarch                            No change
conda-forge/label/python_rc/linux-64                          No change
Could not solve for environment specs
The following packages are incompatible
├─ jupyter_core >=4.12,!=5.0.*  is installable with the potential options
│  ├─ jupyter_core [4.12.0|5.1.0|...|5.7.2] would require
│  │  └─ python >=3.10,<3.11.0a0 , which can be installed;
│  ├─ jupyter_core [4.12.0|5.1.0|...|5.7.2] would require
│  │  └─ python >=3.11,<3.12.0a0 , which can be installed;
│  ├─ jupyter_core [4.12.0|5.1.0|...|5.7.2] would require
│  │  └─ python >=3.8,<3.9.0a0 , which can be installed;
│  ├─ jupyter_core [4.12.0|5.1.0|...|5.7.2] would require
│  │  └─ python >=3.9,<3.10.0a0 , which can be installed;
│  └─ jupyter_core [5.3.1|5.3.2|...|5.7.2] would require
│     └─ python_abi 3.12.* *_cp312, which requires
│        └─ python 3.12.* *_cpython, which can be installed;
└─ python 3.13**  is not installable because it conflicts with any installable versions previously reported.

If no pins is applied, it will install version 4.5.0.

Installed packages

not needed

Environment info

active environment : base
    active env location : /home/shh/miniconda3
            shell level : 1
       user config file : /home/shh/.condarc
 populated config files : /home/shh/miniconda3/.condarc
                          /home/shh/.config/conda/.condarc
          conda version : 24.7.1
    conda-build version : 24.7.1
         python version : 3.12.5.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=zen4
                          __conda=24.7.1=0
                          __glibc=2.35=0
                          __linux=6.9.3=0
                          __unix=0=0
       base environment : /home/shh/miniconda3  (writable)
      conda av data dir : /home/shh/miniconda3/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/shh/miniconda3/pkgs
                          /home/shh/.conda/pkgs
       envs directories : /home/shh/miniconda3/envs
                          /home/shh/.conda/envs
               platform : linux-64
             user-agent : conda/24.7.1 requests/2.32.3 CPython/3.12.5 Linux/6.9.3-76060903-generic pop/22.04 glibc/2.35 solver/libmamba conda-libmamba-solver/24.7.0 libmambapy/1.5.9
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

[bollwyvl]

This feedstock getting an automated migration PR is blocked by conda-forge/pywin32-feedstock#58 (comment).

That migration will also drop pypy, I believe, which would make some of this more flexible, but there would still need to be a build that pulls in pywin32 somewhere, and ideally one that is actually tested.

[minrk]

With #96, you can now mamba install jupyterlab with the 3.13 RC, except on Windows.