From 6e2bcc3d8e93f4e9a5a336159c08ebf8729608c6 Mon Sep 17 00:00:00 2001 From: ndclt Date: Mon, 24 Jun 2019 18:57:01 +0200 Subject: [PATCH] Coherence between example and text (use of to_native) (#58279) (#58283) (cherry picked from commit 4376e88849a7cf3be2613d0d12a49fa839ab2bd3) --- docs/docsite/rst/dev_guide/developing_plugins.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/dev_guide/developing_plugins.rst b/docs/docsite/rst/dev_guide/developing_plugins.rst index 0c84bbd275..6a6226db71 100644 --- a/docs/docsite/rst/dev_guide/developing_plugins.rst +++ b/docs/docsite/rst/dev_guide/developing_plugins.rst @@ -25,7 +25,7 @@ You must write your plugin in Python so it can be loaded by the ``PluginLoader`` Raising errors ============== -You should return errors encountered during plugin execution by raising ``AnsibleError()`` or a similar class with a message describing the error. When wrapping other exceptions into error messages, you should always use the ``to_text`` Ansible function to ensure proper string compatibility across Python versions: +You should return errors encountered during plugin execution by raising ``AnsibleError()`` or a similar class with a message describing the error. When wrapping other exceptions into error messages, you should always use the ``to_native`` Ansible function to ensure proper string compatibility across Python versions: .. code-block:: python