Skip to content

Conversation

@regro-cf-autotick-bot
Copy link
Contributor

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

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

@conda-forge-admin
Copy link
Contributor

conda-forge-admin commented Dec 20, 2024

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 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.

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

@h-vetinari h-vetinari marked this pull request as draft February 9, 2025 11:40
@h-vetinari
Copy link
Member

See tensorflow/tensorflow#78774

@hmaarrfk hmaarrfk force-pushed the rebuild-python313-0-1_h198bfa branch from 53dafb2 to 11c3b91 Compare February 9, 2025 17:20
@hmaarrfk
Copy link
Contributor

hmaarrfk commented Feb 9, 2025

I'm curious to try... the comments seem to be from early adopters that haven't tried to compile things in detail. Lets see how far it goes....

@h-vetinari
Copy link
Member

I'm curious to try... the comments seem to be from early adopters that haven't tried to compile things in detail. Lets see how far it goes....

That's very optimistic... There's one of the (former?) upstream maintainers commenting a lot, and the arch folks apparently also failed after patching in the requirements file. I think this will have to wait for the next release.

@hmaarrfk
Copy link
Contributor

hmaarrfk commented Feb 9, 2025

i definitely missed the arch comment....

@h-vetinari
Copy link
Member

Seems like the release branch for 2.19 was cut without support for 3.13 🤦

But at least it seems like the arch folks apparently have a working set of patches, if you're motivated.

@hmaarrfk
Copy link
Contributor

is it surprising that they don't need the patches to the cuda stuff? or are arch people really spending days recompiling their setup on every update?

@loqs
Copy link

loqs commented Feb 15, 2025

is it surprising that they don't need the patches to the cuda stuff? or are arch people really spending days recompiling their setup on every update?

Arch updated to CUDA 12.8.0 and CUDNN 9.7.0 https://gitlab.archlinux.org/archlinux/packaging/packages/tensorflow/-/commit/c5174a2697834ad9f16217d52697fe5bb6cd1895 a few commits before the python 3.13 update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants