From d57e9a646583e55213d0f5ca88c1f91062569288 Mon Sep 17 00:00:00 2001 From: Alexandre Passos Date: Thu, 14 Jun 2018 15:45:19 -0700 Subject: Clarify reuse documentation in variable_scope and eager. PiperOrigin-RevId: 200631958 --- tensorflow/python/ops/variable_scope.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tensorflow/python/ops/variable_scope.py b/tensorflow/python/ops/variable_scope.py index 23234e2e61..f49e2d314d 100644 --- a/tensorflow/python/ops/variable_scope.py +++ b/tensorflow/python/ops/variable_scope.py @@ -1908,7 +1908,8 @@ class variable_scope(object): for this scope as well as all sub-scopes; if tf.AUTO_REUSE, we create variables if they do not exist, and return them otherwise; if None, we inherit the parent scope's reuse flag. When eager execution is enabled, - this argument is always forced to be tf.AUTO_REUSE. + new variables are always created unless an EagerVariableStore or + template is currently active. dtype: type of variables created in this scope (defaults to the type in the passed scope, or inherited from parent scope). use_resource: If False, all variables will be regular Variables. If True, -- cgit v1.2.3