run CI on python=3.13

[keewis]

• Closes Add python 3.13 to CI #9664

Missing libraries:

• dask: dask-expr depends on pyarrow, which will support 3.13 starting with pyarrow>=18.0
• pydap: depends on webob which uses the removed cgi stdlib (see Resolve Deprecation Warnings  pydap/pydap#319 (comment) in the "out-of-scope" section)
• numba: as usual will take some time to support it (and thus we can't test numbagg and sparse)

[keewis]

Interestingly it's conda that you can't install along with python=3.13, but cftime, pandas, and possibly h5py also raise errors (I can't reproduce that locally, though). So I guess we'll have to revisit this in a couple of weeks.

[mathause]

Is there a reason we are installing conda? For the output of conda info and conda list? There is a micromamba info and micromamba list output in the Setup micromamba step which we could refer to instead.

[keewis]

we use conda to call conda info -a, which contains information micromamba info does not include (and I don't know whether micromamba info -a exists). In theory we could use mamba info -a as well, but that also doesn't provide packages for python 3.13.

[dcherian]

shall we just stick to all-but-dask given what we've had to comment out? If we're going to change this line, it'd be nice to drop 3.12 which we can't at the moment...

[dcherian]

Ah dask/dask#11456 was just merged so this is coming...

[keewis]

I'm in the progress of checking whether that's still necessary. If yes, then sure.

[keewis]

okay, looks like this will still fail, but not for long. I don't think we can go with all-but-dask, though, since that's still trying to install numba / sparse / numbagg. Until that supports python=3.13 we'll have to live with 3 more CI jobs, I guess.

Edit: looks like we don't need whatever blocked dask from officially supporting python=3.13 (CI seems to pass?)