From 7c61ce153ffcbb75ededa9ece4ea86ae1c19fbc2 Mon Sep 17 00:00:00 2001 From: Evgeni Golov Date: Mon, 26 Nov 2018 22:55:25 +0100 Subject: [PATCH] clarify what `strict` means for the `version` test (#48979) Reference the fact that we use the `StrictVersion` parser instead of `LooseVersion` from `distutils` in this case. --- docs/docsite/rst/user_guide/playbooks_tests.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/docsite/rst/user_guide/playbooks_tests.rst b/docs/docsite/rst/user_guide/playbooks_tests.rst index f7fbdf03a1a..68164e191ba 100644 --- a/docs/docsite/rst/user_guide/playbooks_tests.rst +++ b/docs/docsite/rst/user_guide/playbooks_tests.rst @@ -84,8 +84,7 @@ The ``version`` test accepts the following operators:: <, lt, <=, le, >, gt, >=, ge, ==, =, eq, !=, <>, ne -This test also accepts a 3rd parameter, ``strict`` which defines if strict version parsing should -be used. The default is ``False``, but this setting as ``True`` uses more strict version parsing:: +This test also accepts a 3rd parameter, ``strict`` which defines if strict version parsing as defined by ``distutils.version.StrictVersion`` should be used. The default is ``False`` (using ``distutils.version.LooseVersion``), ``True`` enables strict version parsing:: {{ sample_version_var is version('1.0', operator='lt', strict=True) }}