2016-10-25 22:12:52 +00:00
================
Python 3 Support
================
2017-09-25 19:36:58 +00:00
Ansible 2.2, 2.3, and 2.4 feature a tech preview of Python 3 support. This topic discusses how you can test to make sure your modules and playbooks work with Python 3.
2016-10-25 22:12:52 +00:00
2017-08-04 20:57:09 +00:00
.. note :: Ansible supports Python version 3.5 and above only.
2016-10-25 22:12:52 +00:00
2017-12-15 20:04:53 +00:00
.. note :: Technology preview features provide early access to upcoming product innovations,
2016-10-25 22:12:52 +00:00
enabling you to test functionality and provide feedback during the development process.
2017-12-15 20:04:53 +00:00
Please be aware that tech preview features may not be functionally complete and are not
2016-10-25 22:12:52 +00:00
intended for production use. To report a Python 3 bug, please see `Community Information & Contributing <http://docs.ansible.com/ansible/community.html#i-d-like-to-report-a-bug> `_ .
Testing Python 3 with commands and playbooks
2017-09-02 03:49:01 +00:00
--------------------------------------------
2016-10-25 22:12:52 +00:00
2017-12-15 20:04:53 +00:00
* Run Ansible 2.2+ - See :ref: `from_source`
2016-10-25 22:12:52 +00:00
* To test Python 3 on the controller, run your ansible command via
2017-04-12 17:49:26 +00:00
`` python3 `` . For example:
2016-10-25 22:12:52 +00:00
2017-04-04 18:18:19 +00:00
.. code-block :: shell
2016-10-25 22:12:52 +00:00
2017-09-28 03:21:38 +00:00
$ python3 /usr/bin/ansible localhost -m ping
$ python3 /usr/bin/ansible-playbook sample-playbook.yml
2016-10-25 22:12:52 +00:00
2017-09-02 03:49:01 +00:00
You can also install Ansible using :program: `pip` for Python3 which will make the default
:command: `/usr/bin/ansible` run with Python3:
.. code-block :: shell
2017-09-28 03:21:38 +00:00
$ virtualenv --python=python3 py3-ansible
$ source ./py3-ansible/bin/activate
2017-09-02 03:49:01 +00:00
$ pip3 install ansible
2017-09-28 03:21:38 +00:00
$ ansible --version | grep "python version"
python version = 3.6.2 (default, Sep 22 2017, 08:28:09) [GCC 7.2.1 20170915 (Red Hat 7.2.1-2)]
On systems with SELinux installed, such as Red Hat Enterprise Linux or Fedora, the SELinux Python libraries also need to be copied over.
.. code-block :: shell
$ cp -r -v /usr/lib64/python3.*/site-packages/selinux/ ./py3-ansible/lib64/python3.* /site-packages/
$ cp -v /usr/lib64/python3.*/site-packages/* selinux*.so ./py3-ansible/lib64/python3.* /site-packages/
2017-09-02 03:49:01 +00:00
.. note :: Individual Linux distribution packages may be packaged for Python2 or Python3. When running from
distro packages you'll only be able to use Ansible with the Python version for which it was
installed. Sometimes distros will provide a means of installing for several Python versions
(via a separate package or via some commands that are run after install). You'll need to check
with your distro to see if that applies in your case.
2016-10-25 22:12:52 +00:00
Testing Python 3 module support
--------------------------------
* Set the ansible_python_interpreter configuration option to
2017-04-04 18:18:19 +00:00
:command: `/usr/bin/python3` . The `` ansible_python_interpreter `` configuration option is
usually set per-host as an inventory variable associated with a host or group of hosts:
2016-10-25 22:12:52 +00:00
2017-04-04 18:18:19 +00:00
.. code-block :: ini
2016-10-25 22:12:52 +00:00
2017-04-04 18:18:19 +00:00
# Example inventory that makes an alias for localhost that uses python3
[py3-hosts]
localhost-py3 ansible_host=localhost ansible_connection=local
2016-10-25 22:12:52 +00:00
2017-04-04 18:18:19 +00:00
[py3-hosts:vars]
ansible_python_interpreter=/usr/bin/python3
2016-10-25 22:12:52 +00:00
2018-04-02 18:53:24 +00:00
See :ref: `intro_inventory` for more information.
2017-04-04 18:18:19 +00:00
* Run your command or playbook:
.. code-block :: shell
2017-09-28 03:21:38 +00:00
$ ansible localhost-py3 -m ping
$ ansible-playbook sample-playbook.yml
2017-04-04 18:18:19 +00:00
2018-04-02 18:53:24 +00:00
Note that you can also use the `-e` command line option to manually
2017-04-04 18:18:19 +00:00
set the python interpreter when you run a command. For example:
.. code-block :: shell
2017-09-28 03:21:38 +00:00
$ ansible localhost -m ping -e 'ansible_python_interpreter=/usr/bin/python3'
$ ansible-playbook sample-playbook.yml -e 'ansible_python_interpreter=/usr/bin/python3'
2017-04-04 18:18:19 +00:00
What to do if an incompatibility is found
-----------------------------------------
If you find a bug while testing modules with Python3 you can submit a bug
2017-04-04 18:40:41 +00:00
report on `Ansible's GitHub project
2017-04-12 17:49:26 +00:00
<https://github.com/ansible/ansible/issues/> `_. Be sure to mention Python3 in
2017-04-04 18:18:19 +00:00
the bug report so that the right people look at it.
If you would like to fix the code and submit a pull request on github, you can
2018-04-02 18:53:24 +00:00
refer to :ref: `developing_python3` for information on how we fix
2017-04-04 18:18:19 +00:00
common Python3 compatibility issues in the Ansible codebase.