-
Notifications
You must be signed in to change notification settings - Fork 6
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
Move from tensorflow.keras
to keras
#2134
Comments
There is no guarantee either way, some years ago this was their position: https://github.com/keras-team/keras/releases/tag/2.3.0 I'd argue that we should keep using |
I think a change of position in 5 years is still more stable than other programs we use I've needed to add this already. |
Conda packages can always be a mess, separating keras and tensorflow may also result in problems with compatibility between versions. Feel free to do this if you want to change it, but I don't think that at this point we can say that separating them is clearly the better choice. |
No. This doesn't generate (new) problems because most of the calls are already using the separate package. If you do But we risk using features that don't actually exist in the separated
|
This will make the code more general. If we can remove the tensorflow dependency as much as possible (it would be impossible right now to remove it completely) that would be great (it means we could test pytorch for instance).
At the moment (tf 2.17)
tensorflow.keras
is still provided, but it is not a given that it will continue like that and in particular the conda forge package for macos (maybe a bug on their side, I'm not sure) seems to be missingtensorflow.keras
.The text was updated successfully, but these errors were encountered: