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/18174914115 - please use this URL for debugging.}

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

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The magma output has been superseded by libmagma-devel.
• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

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

[xhochy]

My understanding is that this will need the PyTorch 2.10 release. Thus, I set the PR to draft so that it doesn't get recreated until this has landed.

[xhochy]

See also pytorch/pytorch#156856

[h-vetinari]

It might be possible for the upcoming 2.9 with some backports. We'll see. :)

[reneleonhardt]

The tracking issue is still open, and the Python 3.14 support is declared experimental, but wheels have been published 3 weeks ago:
https://github.com/pytorch/pytorch/releases/tag/v2.9.0
https://pypi.org/project/torch/2.9.0/#files

[h-vetinari]

We have our hands full with #433 at the moment, but initial testing by @mgorny showed that the 3.14 do not pass pytorch's own test suite. As such, I don't think this will end up being publishable, except perhaps under an opt-in label.

[rgommers]

The PyTorch 2.9.0 release notes say "We also have 3.14 and 3.14t available as preview with this release.". I wouldn't expect the torch.compile tests in particular to pass, but it was close enough that they decided to put wheels up on PyPI. Just matching upstream in functionality (gaps) seems acceptable to me in principle.

[h-vetinari]

I'd be a tad more careful. There's no indication of the fact that it's only a preview when installing through conda-forge, and instead of disappointing users who don't know the details, I'd prefer to make it opt-in for power-users who accept the risk.