tensorflow model: fix TensorflowModelMixin usage #201
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
antoinejeannot
dismissed stale reviews from ldeflandre and mathilde-leval
via
8128fee
|
PTAL @ldeflandre |
ldeflandre
approved these changes
Nov 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
Following the discussions around MRO, I noticed an issue with regards to the way we use the
TensorflowModelMixin.Before: its initialization is never called, hence the
ImportErroriftensorflowis missing is never raised and a cryptic error is raised later onAfter this PR: its initialization is called, and directly raises the
ImportErroriftensorflowis missing.Thanks for your review