From bca9d9bf67f6afbcabfeda36939dea4e461ba4bc Mon Sep 17 00:00:00 2001
From: Steven Robertson <srtrumpetaggie@gmail.com>
Date: Wed, 30 Oct 2019 15:05:02 -0700
Subject: [PATCH] added info to ansible_detailed.rst explaining new
 ansible_python_interpreter functionality

---
 docs/ansible_detailed.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/ansible_detailed.rst b/docs/ansible_detailed.rst
index 22d7223f..c8b5d972 100644
--- a/docs/ansible_detailed.rst
+++ b/docs/ansible_detailed.rst
@@ -240,7 +240,7 @@ Noteworthy Differences
 ..
     * The ``ansible_python_interpreter`` variable is parsed using a restrictive
       :mod:`shell-like <shlex>` syntax, permitting values such as ``/usr/bin/env
-      FOO=bar python``, which occur in practice. Ansible `documents this
+      FOO=bar python`` or ``source /opt/rh/rh-python36/enable && python``, which occur in practice. Jinja2 templating is also supported for complex task-level interpreter settings. Ansible `documents this
       <https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html#ansible-python-interpreter>`_
       as an absolute path, however the implementation passes it unquoted through
       the shell, permitting arbitrary code to be injected.