-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tensorflow 2.18.0-rc1 #405
Conversation
…nda-forge-pinning 2024.10.17.15.21.02
Theoretically this supports NumPy 2 and Python 3.13 but we first need to migrate |
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 ( |
Python 3.13 depends on conda-forge/h5py-feedstock#148 |
Does building complete? I'm wondering if we can at least add a test to stay aware of things like: |
For the non-CUDA variants, it works. I have cancelled the jobs as I realised that the CUDA jobs just hang at the Is there anything in #296 (comment) which we could test on a non-CUDA system? |
I really tried hard to read your comments on the jax repo to see if it was something I could fix myself.
I was hoping we could "force" some compilation (but not execution). That said I don't know enough about the workings of tensorflow for this. |
AFAIR 2.18 is also the first version to support numpy 2.0 |
I have both added locally and will push them with some fixes in the next days. If anyone is eager to be faster, happy to see it but let me know 🙃 |
would you be willing to push your fixes? curious if we can get the protobuf going with 2.18.0 now that it is release. |
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)