In particular, this enables you to run tests locally (since you won't need to compile TF to test Keras anymore) and it improves CI times.
-
-
Show this thread
-
If you want to make a change in Keras, please open a PR in https://github.com/keras-team/keras …, rather than the TensorFlow repo.
Show this thread -
Since folks are asking: this change only affects the development process for contributors. It doesn't affect any public API. You should still access Keras as tf.keras (which is the only Keras version). For you as a user, absolutely nothing changes, now or in the future.
Show this thread
End of conversation
New conversation -
-
-
Any docs that we can refer to for requesting new features or will there be a form like the TensorFlow one for the next release timelines and reviews?
-
I'd encourage you to post on the TensorFlow forum to request a feature.
- Show replies
New conversation -
-
-
Does this mean TF will work on developing yet another API for itself?
-
No. This change only affects the development process for contributors. It doesn't affect any public API. You should still access Keras as tf.keras.
End of conversation
New conversation -
-
-
What will happen to tf.keras? Will its APIs diverge from those in keras?
-
This change only affects the development process for contributors. It doesn't affect any public API. You should still access Keras as tf.keras. That's the only Keras version.
End of conversation
New conversation -
-
-
Will TF have their own, independent Keras implementation, then?
-
This change only affects the development process for contributors. It doesn't affect any public API. You should still access Keras as tf.keras. Which is the same Keras version that's now being developed in its own repo.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.