You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rfcs/20230621-tf-api-deprecation.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -60,7 +60,7 @@ A TensorFlow API is considered fully deprecated when:
60
60
* Ex: if `tf.bar` uses deprecated `tf.foo`, calling `tf.bar` should not trigger a warning.
61
61
* As appropriate, examples (e.g. experimental Colab notebooks) are created demonstrating the replacement of any deprecated modules or methods.
62
62
* The API is covered by a publicly available _strict mode_ which users can optionally enable to convert warnings to failures, with error messages that guide them to replacements.
63
-
* Strict mode is a globally applied state, switched on with `tf.exprimental.enable_strict_mode()`.
63
+
* Strict mode is a globally applied state, switched on with `tf.experimental.enable_strict_mode()`.
64
64
* Once enabled, ignorable runtime warnings for deprecated APIs will instead be replaced with errors, detailing the deprecation and suggested alternatives.
65
65
* Alongside release in TF Nightly, messaging is sent through appropriate communication channels to inform of the upcoming deprecation, rationale, and available substitutes.
66
66
* Depending on the nature and scope of deprecation, this may be done at the individual API level or in interrelated block(s).
0 commit comments