-
Notifications
You must be signed in to change notification settings - Fork 74k
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
pip install tf-nightly[and-cuda]
fails for recent nightlies
#62035
Comments
Can reproduce this on ubuntu and colab. This issue looks related NVIDIA/TensorRT#2933 Potentially a simple fix, I am not sure we really need to be pinning |
I found failure of same package i.e |
It seems this one does not exist: |
Hi, I am unable to install tensorflow nightly. Any suggestions ? I am running tensor flow 2.13.1 ? |
Could you please confirm the install command and logs ? Please note that current nightly version is 2.16.0-dev20231018. |
I ran into the same issue with Version 2.15.0 rc0.
|
This issue still exists in the stable 2.15.0 version. |
Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
nightly
Custom code
No
OS platform and distribution
Google Colab
Mobile device
No response
Python version
3.10
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
The issue
Attempting to run
pip install tf-nightly[and-cuda]
will download a ton of nightly candidates before installing one from mid-September (before tf bumped to cuda12).Attempting to pin the more recent versions shows the error with recent nightlies.
You can work around this with
pip install tf-nightly[and-cuda] --extra-index-url https://pypi.nvidia.com
.What should happen
pip install tf-nightly[and-cuda]
should not self conflict, and recent nighties should be installable via PyPI.Standalone code to reproduce the issue
https://colab.research.google.com/gist/mattdangerw/00acd58e43aabe7f80a74d595788bd86/tf-nightly-and-cuda.ipynb
Relevant log output
No response
The text was updated successfully, but these errors were encountered: