WIP: Bump python from 3.12 to 3.14

[weiji14]

Bumps python from 3.12.12 to 3.14.3.

• Release notes
• Changelog
• Commits

Previous PR at #643

[pangeo-bot]

/condalock
Automatically locking new conda environment, building, and testing images...

[weiji14]

Logs for conda-lock CI at https://github.com/pangeo-data/pangeo-docker-images/actions/runs/22552398409/job/65324292243#step:4:74:

Could not solve for environment specs
The following packages are incompatible
├─ icechunk is installable with the potential options
│  ├─ icechunk [0.1.0|0.1.1|...|1.1.9] would require
│  │  └─ python_abi 3.11.* *_cp311, which can be installed;
│  ├─ icechunk [0.1.0|0.1.1|...|1.1.9] would require
│  │  └─ python_abi 3.12.* *_cp312, which can be installed;
│  └─ icechunk [0.2.11|0.2.12|...|1.1.9] would require
│     └─ python_abi 3.13.* *_cp313, which can be installed;
...

Blocked by conda-forge/icechunk-feedstock#109. Might be some other packages too.

[weiji14]

/condalock
https://github.com/pangeo-data/pangeo-docker-images/actions/runs/22593262827

[weiji14]

Next package to handle is python-blosc:

Could not solve for environment specs
The following packages are incompatible
├─ python-blosc is installable with the potential options
...
│  ├─ python-blosc 1.8.3 would require
│  │  └─ python_abi * *_cp38, which can be installed;
│  ├─ python-blosc [1.11.1|1.11.2|1.11.3|1.11.4] would require
│  │  └─ python_abi 3.12.* *_cp312, which can be installed;
│  └─ python-blosc [1.11.2|1.11.3|1.11.4] would require
│     └─ python_abi 3.13.* *_cp313, which can be installed;
...

Seems like conda-forge/python-blosc-feedstock#62 was closed but not regenerated, will try to kick the bot a bit.

Edit: opened conda-forge/python-blosc-feedstock#64

[weiji14]

/condalock

[weiji14]

Cool, pangeo-notebook and pytorch-notebook are Python 3.14 ready now 🎉 Right now it's ml-notebook that's not solving - https://github.com/pangeo-data/pangeo-docker-images/actions/runs/22639508195/job/65611383161#step:4:122:

Could not solve for environment specs
The following packages are incompatible
├─ ...
│     ...
└─ tensorflow >=2.17.0 cuda12* is installable with the potential options
   ├─ tensorflow [2.17.0|2.18.0|2.19.0|2.19.1] would require
   │  ├─ __cuda, which can be installed;
   │  └─ python_abi 3.10.* *_cp310, which can be installed;
   ├─ tensorflow [2.17.0|2.18.0|2.19.0|2.19.1] would require
   │  ├─ __cuda, which can be installed;
   │  └─ python_abi 3.11.* *_cp311, which can be installed;
   ├─ tensorflow [2.17.0|2.18.0|2.19.0|2.19.1] would require
   │  ├─ __cuda, which can be installed;
   │  └─ python_abi 3.12.* *_cp312, which can be installed;
   ├─ tensorflow [2.17.0|2.18.0] would require
   │  ├─ __cuda, which can be installed;
   │  └─ python_abi 3.9.* *_cp39, which can be installed;
   └─ tensorflow [2.18.0|2.19.0] would require
      ├─ __cuda, which can be installed;
      └─ tensorflow-base [2.18.0 cuda128py310h09ee966_202|2.18.0 cuda128py310h8355c94_252|...|2.19.0 cuda128py312hd1639bb_202], which requires
         └─ cudnn [>=9.13.0.50,<10.0a0 |>=9.13.1.26,<10.0a0 ], which requires
            └─ cuda-version >=13,<14.0a0 , which requires
               └─ __cuda >=13 , which conflicts with any installable versions previously reported.

Depends on conda-forge/tensorflow-feedstock#452, and also upstream tensorflow/tensorflow#102890. Might be a long wait... so maybe I should do the intermediate python 3.13 first in a separate PR.