Rebuild for python 3.14

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update python314.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/21070765243 - please use this URL for debugging.}

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint --conda-forge . from the recipe directory. You can also examine the workflow logs for more detail.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/21071528917. Examine the logs at this URL for more detail.}

[lucascolley]

@hmaarrfk any idea why the aarch and ppc builds are failing with this?

$SRC_DIR/conda_build.sh: line 8: $SRC_DIR_env/bin/python: cannot execute binary file: Exec format error

[hmaarrfk]

unfortunately i do not.

but it seems like something is not working with our qemu setup since yesterday.

I've opened #22 as an example of how I troubleshoot things. but I really don't want to follow through with troubleshooting it.

it seems that the "version of the recipe" before my PR was acceptable
#20 (comment)
and perhaps that is the right move.

Perhaps @h-vetinari is more aware of a change that happened yesterday.

Related discussions
xref: #20
xref: scientific-python/spin#311

[hmaarrfk]

(if it is ok, i've unsubscribe from this, unfortunately I cannot commit to helping maintain this project and need to get it off my notifications -- #18)

[stefanv]

I greatly appreciate the efforts here, but I wonder if it wouldn't be simpler to just patch spin to work around the Python 3.10 issue so we can continue using the existing recipe. I will take a look later today.

[conda-forge-admin]

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 (recipe/recipe.yaml) and found it was in an excellent condition.

[hmaarrfk]

I think it was a configuration blunder on the longer and azure

[lucascolley]

thanks Mark!

[stefanv]

I have written a patch for spin, which will hopefully make it possible to return to our previous conda-forge recipe: scientific-python/spin#312