Skip to content
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

legacy_tf_layers missing from keras 2.13, 2.14 and 2.15 #18839

Closed
hmaarrfk opened this issue Nov 28, 2023 · 4 comments
Closed

legacy_tf_layers missing from keras 2.13, 2.14 and 2.15 #18839

hmaarrfk opened this issue Nov 28, 2023 · 4 comments
Assignees
Labels

Comments

@hmaarrfk
Copy link
Contributor

image

inspecting the pypi packages it seems that the folder legacy_tf_layers is simply missing.

I couldn't find an obvious PR or issue that discussed removing the folder. was it removed in error?

@sachinprasadhs
Copy link
Collaborator

sachinprasadhs commented Nov 28, 2023

Hi, I can see the legacy tf_keras_layers in the tf_keras repo here https://github.com/keras-team/tf-keras/tree/master/tf_keras/legacy_tf_layers.
For 2.14, https://github.com/keras-team/keras/tree/v2.14.0/keras/legacy_tf_layers
Keras is now updated to Keras 3 which supports multi-backend like TensorFlow, JAX and PyTorch and the above mentioned directory structure will not be available in Keras 3.

@hmaarrfk
Copy link
Contributor Author

I don't disagree that the folder is there in the repository, it simply is missing from the pypi wheel distribution.

Am I missing something? The screenshots I took were from the wheels.

@hmaarrfk
Copy link
Contributor Author

(Also thank you for your fast response!!!!)

@hmaarrfk
Copy link
Contributor Author

sorry for the noise.

I think ultimately it is an issue with tf_slim that was using an internal API

I've asked them for a new release since they have already "fixed" the issue in their repo

google-research/tf-slim#24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants