-
Notifications
You must be signed in to change notification settings - Fork 291
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
MacOs poetry install of tensorflow failing #1617
Comments
I've solved the h5py installation issue. Trying to install tensorflow again I get the same error from |
I tested out installing previous versions of |
Same problem here. Have a Dockerfile and docker-compose I use at work.
|
I'm also having this issue. But on Ubuntu not macOS. |
I faced similar problems. The hdf5 issue, I solved it using this SO answer I was able to install tensorflow-io-gcs-filesystem following the instructions at #1298 (comment) Then, I used tensorflow-macos at https://pypi.org/project/tensorflow-macos/ |
@joaquincabezas thank you! I followed your instructions, however I still get the same error with • Installing tensorflow-io-gcs-filesystem (0.26.0): Failed
RuntimeError
Unable to find installation candidates for tensorflow-io-gcs-filesystem (0.26.0)
at ~/miniconda3/envs/tempr/lib/python3.9/site-packages/poetry/installation/chooser.py:72 in choose_for
68│
69│ links.append(link)
70│
71│ if not links:
→ 72│ raise RuntimeError(
73│ "Unable to find installation candidates for {}".format(package)
74│ )
75│
76│ # Get the best link |
the link I used was for 0.21, guess it should be similar but for 0.26 (check out also https://medium.com/dive-into-ml-ai/installing-tensorflow-natively-on-mac-m1-in-2022-1357e9b7a201). Also I found some posts complaining about this for Python 3.8 but they were successfully installing it with Python 3.9. Which version are you using? |
I have the same issue when dockerizing an application that depends on
|
Still encountering this issue as well. Any updates? |
I'm also experiencing this issue |
The same experience, any progress? |
Although this issue has MacOS in its title, I also run into this issue on WIndows. |
I've also the same problem on my Mac. |
Try building the wheel with |
I found documentation from Apple on setting up TensorFlow in Apple Silicon and x86 architectures: https://developer.apple.com/metal/tensorflow-plugin/ Can you test if this solves it for you? |
Also encountering this issue, advocating for a solution that is not platform dependent and/or changes the name of the dependency in |
I was also having this issue on Windows 10 while installing tensorflow-io-gcs-filesystem version 0.32.0. In the end it worked after I did the following:
Not sure if step 1 is absolutely necessary, maybe just using version 0.31.0 already does the trick. I think there is a general problem with poetry and tensorflow, because I encountered more problems:
|
I was also having this issue on Windows 10 while installing tensorflow-io-gcs-filesystem version 0.32.0. I was trying to install it for Flower Framework and got the same problem. For me, executing |
I was also having this issues, and installing tensorflow-metal solved it for me:
|
I'm Windows 10.
|
Seeing an odd issue with just getting
Installing tensorflow-io-gcs-filesystem (0.35.0): Failed
RuntimeError
Unable to find installation candidates for tensorflow-io-gcs-filesystem (0.35.0)
69│
70│ links.append(link)
71│
72│ if not links:
→ 73│ raise RuntimeError(f"Unable to find installation candidates for {package}")
74│
75│ # Get the best link
76│ chosen = max(links, key=lambda link: self._sort_key(package, link))
77│
Cannot install tensorflow-io-gcs-filesystem. However, simply changing to the previous version works fine:
|
Issue still exists for mac m1 pro, solved it by @stefansjs #1617 (comment) |
Hello
I'm trying to install tensorflow on MacOs with poetry and I get the following error:
For a more complete view (I hope) here is the operation and full log:
I see that h5py also fails, I'll check that too. But I also notice that your Mac CI (Github) failed some hours ago.
The text was updated successfully, but these errors were encountered: