Qianli Scott Zhu

I think this is all addressed by @ianstenbit in https://github.com/keras-team/keras-cv/pull/748 and https://github.com/keras-team/keras-cv/pull/751

@fchollet, please take a look for this PR again.

Thanks all for the inputs. I think the most approvable way to do this so far is either using TF savedmodel to ONNX, or torch backend (less mature on Keras...

Discussed this in the team meeting. In general we will leverage each backend for their own way to export to ONNX, eg TF has its own way to convert tf...

Adding Neel since this is related to saving/exporting.

the proper imort of keras is `tensorflow.keras`, or `import tensorflow as tf; tf.keras`. `tensorflow.python.keras` is NOT the correct way to import keras, and it points to the legacy keras code...

For the actual keras code, it stays in `keras` package, and the __init__.py under tensorflow will pick it up (rather than pickup from tensorflow/python/keras).

tf.keras was always the public API to access. For TF 1.4, I don't think keras was part of the TF API at the time, so you can't even access tensorflow.python.keras...

Not sure why the issue is closed, but I think this fix is needed for the issue. I will merge it now.

SGTM.