Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Switch to TensorFlow 2.0 and tf.keras
See original GitHub issueFrom the Keras site:
The current release is Keras 2.3.0, which makes significant API changes and add support for TensorFlow 2.0. The 2.3.0 release will be the last major release of multi-backend Keras. Multi-backend Keras is superseded by
tf.keras.
Maybe it’s time to upgrade?
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
Migrate to TensorFlow 2
Migrate from TensorFlow 1.x to TensorFlow 2 · Run the automated script to convert your TF1. · Remove old tf. · Rewrite your...
Read more >Keras vs. tf.keras: What's the difference in TensorFlow 2.0?
And most importantly, going forward all deep learning practitioners should switch their code to TensorFlow 2.0 and the tf.keras package.
Read more >Step-by-step Guide to Install TensorFlow 2 | by Chitta Ranjan
TF 1.x also supports Keras, but in 2.0 Keras is integrated tightly with the rest of the TensorFlow platform. 2.0 is providing a...
Read more >2019 (March) Converting Code to Run on TensorFlow 2.0 ...
How to Convert from Keras / Tensorflow to PyTorch · I challenged ChatGPT to code and hack (Are we doomed?) · 2020, TensorFlow...
Read more >Releases · tensorflow/tensorflow - GitHub
If you want to keep using an old checkpoint, please change your optimizer to tf.keras.optimizer.legacy.XXX (e.g. tf.keras.optimizer.legacy.Adam ).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I am hoping to work on this and on ONNX support during the end of year holidays.
From the TensorFlow 1.15.0 release (Oct 16, 2019):
That is now more than a year ago. I didn’t find the planned support for it.
On one of our repos we got the automatic low severity security notifications:
Those were fixed in TensorFlow 2.4.0 (Dec 14, 2020). There wasn’t a related TensorFlow 1.x release with those fixes. As far as I can tell, the security advisories do not mention it not affecting 1.x (just that it affects
< 2.4.0).Additionally TensorFlow 1.15.4 doesn’t support Python 3.8+ (according to PyPI). Whereas TensorFlow 2.4.0 supports 3.8, but not Python 2 (see PyPI).
Which makes me think that it may not be far off before the support is officially dropped.