PR #18125: Dealing with the problem that tf.name_scope is not reflected #17538

[copybara-service]

PR #18125: Dealing with the problem that tf.name_scope is not reflected keras-team/tf-keras#269

Imported from GitHub PR #18125

Fixed the problem that tf.name_scope is ignored even if tf.keras.internal.apply_name_scope_on_model_declaration is used.

related issues

• tf.name_scope is ignored when constructing a model using the functional API tf-keras#269
• Tensorflow 2.0 tf.name_scope has no effect on weights created by keras functional api tensorflow/tensorflow#27298

PS. Thanks to @slanzmich for finding this solution.
Copybara import of the project:

--
6ab4ccf by kenkoba [email protected]:

Format keras/engine/base_layer.py and _test.py

I use black --line-length 80 keras/engine/base_layer.py and _test.py
When applied to everything below keras, the difference became large and
confusing, so I restricted it.

--
dffd2ad by kenkoba [email protected]:

Reproduce an issue where tf.name_scope is ignored

ref: keras-team/tf-keras#269

--
e33503a by kenkoba [email protected]:

Use the name_scope with tf.get_current_name_scope

Using current_name_scope in self._name_scope() seemed to be difficult to
handle because it is a deep value managed by python's threading through
tf.internal.get_name_scope

--
3673996 by kenkoba [email protected]:

Rid of my bad habits

Merging this change closes #18125

FUTURE_COPYBARA_INTEGRATE_REVIEW=#18125 from DameNianch:refer-name_scope 3673996

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.