-
Notifications
You must be signed in to change notification settings - Fork 282
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
Error: The h5py Python package is required to use pre-built Keras models #361
Comments
It's failed in have_h5py() function. |
i am having the same issue! |
I am having the same issue and don't see a resolution in this thread- @skeydan any reason this was closed? Could you point me to the solution if its in this thread? I've tried to implement everything above but still have the same problem. Thank you! |
@skeydan this worked for me:
Solution description:@obarisk mentioned:
I created an R test script with reticulate to make sure that worked:
If failed, initially with:
This indicates the libraries are missing from |
Thanks for posting your solution! |
I had this exact issue from trying to run Keras without installing tensorflow. So if someone else has this issue, make sure you've installed tensorflow ` library(tensorflow) install_tensorflow() |
I'm having the same problem.. I have tensorflow installed but I get the following error when I try to run the
|
hi @luostrowski a couple thoughts that might help:
|
|
Hi @ras44 and @t-kalinowski, Thank you both for the replies! I figured it out the problem, somehow the code was importing Python in a virtual environment different than the one I had h5py installed. Once I adjusted this, the script worked. |
To reproduce the issue start a docker container
within docker prep python and install
keras
package in RWhich finally reports
So I've checked if the
h5py
package is correctly installed:Which looks OKish. What am I doing wrong?
The issue seems related to https://stackoverflow.com/questions/46819212/error-in-r-the-h5py-python-package-is-required-to-save-and-load-models but none of the suggested workarounds seem to solve the problem
The text was updated successfully, but these errors were encountered: