This repository has been archived by the owner on Oct 13, 2021. It is now read-only.
Support for recurrent_v2 layers for TF 2.0 #610
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #607, it was observed that TensorFlow versions before 2.0 can have problems converting TF 2.0 compatible models because the classes are expected to be the previous API. For example in TF 1.14 the v2 compatible classes are present in
tensorflow.keras.layers.recurrent_v2
, but do not matchtensorflow.keras.layers
. This PR resolves #607 by adding support for these layers. For versions of TensorFlow that are above 2.0, this is not a problem becausetensorflow.keras.layers
uses the v2 layers.This strategy is tested by expanding the
RNN_CLASSES
list in the tests, so thatrecurrent_v2
classes are tested if present.