-
Notifications
You must be signed in to change notification settings - Fork 56
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
release: v1.9.0 #450
release: v1.9.0 #450
Conversation
Staleness Report: 1.9.0(gpu)
Staleness Report: 1.9.0(cpu)
|
Testing
|
conda-forge::fastapi[version='>=0.110.3,<1.0.0'] | ||
conda-forge::uvicorn[version='>=0.30.1,<1.0.0'] | ||
conda-forge::pytorch-gpu[version='>=2.0.0,<3.0.0'] | ||
conda-forge::tensorflow-gpu[version='>=2.14.0,<3.0.0'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did we make this change ?
Is tensorflow-gpu officially maintained ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it's built from the same feedstock as tensorflow (tensorflow-feedstock) and holds gpu-specific builds
GPU and CPU variants have different versions of tensorflow. We can keep them consistent at 2.14.0 |
We calculate the closure separately so we can get the highest versions, given the constraints. GPU has additional constraint but I don't think we need to dock CPU because of that. Customers are used to 2.15 and we should keep it wherever possible. |
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.