Rebuild for python 3.14 - #19
Conversation
|
@conda-forge-admin, please rerender |
|
Hi! This is the friendly automated conda-forge-webservice. It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details. Please close this pull request and remake it from a fork of this feedstock. Have a great day! |
1 similar comment
|
Hi! This is the friendly automated conda-forge-webservice. It appears you are making a pull request from a branch in your feedstock and not a fork. This procedure will generate a separate build for each push to the branch and is thus not allowed. See our documentation for more details. Please close this pull request and remake it from a fork of this feedstock. Have a great day! |
|
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
|
Closing — opened from a branch on the feedstock by mistake. Reopening the same two commits from a fork. |
Opt in to conda-forge's
python314migration so anuga ships CPython 3.14 packages.Why now
The migration PR (#8) was closed back in March because the build genuinely failed:
That cap is gone. anuga upstream now declares
requires-python = ">=3.10, <3.15"with aProgramming Language :: Python :: 3.14classifier, and 3.3.8 already shipscp314wheels onPyPI for linux, macOS (x86_64 + arm64) and Windows. All runtime dependencies have py314 builds
(
meshpy,pymetis,netcdf4,scipy,numpy,matplotlib-base), and the rest(
xarray,dill,utm,meson-python,pybind11) arenoarch.Because the bot only opens one PR per migration and #8 was closed, it never re-offered it — so
this opts in manually.
Changes
.ci_support/migrations/python314.yaml(copied verbatim from conda-forge-pinning)Rerender to follow via
@conda-forge-admin, please rerender.Checklist