From abc8b0ae73af6c7d303c0bd25cc9ad6b5bba1d3a Mon Sep 17 00:00:00 2001 From: Toshio Kuratomi Date: Tue, 28 Jan 2020 07:32:03 -0800 Subject: [PATCH] This was changed to python 2.7 but should have remained python 2.6 (#66836) * Modules are still python-2.6+ unless there's a compelling reason not to be. --- docs/docsite/rst/dev_guide/developing_modules_checklist.rst | 2 +- docs/docsite/rst/dev_guide/developing_modules_in_groups.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/dev_guide/developing_modules_checklist.rst b/docs/docsite/rst/dev_guide/developing_modules_checklist.rst index 0ec2811e73a..f5c4fe84676 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_checklist.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_checklist.rst @@ -16,7 +16,7 @@ To contribute a module to Ansible, you must: * write your module in either Python or Powershell for Windows * use the ``AnsibleModule`` common code -* support Python 2.7 and Python 3.5 - if your module cannot support Python 2.7, explain the required minimum Python version and rationale in the requirements section in ``DOCUMENTATION`` +* support Python 2.6 and Python 3.5 - if your module cannot support Python 2.6, explain the required minimum Python version and rationale in the requirements section in ``DOCUMENTATION`` * use proper :ref:`Python 3 syntax ` * follow `PEP 8 `_ Python style conventions - see :ref:`testing_pep8` for more information * license your module under the GPL license (GPLv3 or later) diff --git a/docs/docsite/rst/dev_guide/developing_modules_in_groups.rst b/docs/docsite/rst/dev_guide/developing_modules_in_groups.rst index 147d103df1d..cee49f019e3 100644 --- a/docs/docsite/rst/dev_guide/developing_modules_in_groups.rst +++ b/docs/docsite/rst/dev_guide/developing_modules_in_groups.rst @@ -25,7 +25,7 @@ Although it's tempting to get straight into coding, there are a few things to be * Read though all the pages linked off :ref:`developing_modules_general`; paying particular focus to the :ref:`developing_modules_checklist`. * New modules must be PEP 8 compliant. See :ref:`testing_pep8` for more information. -* Starting with Ansible version 2.7, all new modules must :ref:`support Python 2.7+ and Python 3.5+ `. If this is an issue, please contact us (see the "Speak to us" section later in this document to learn how). +* Starting with Ansible version 2.4, all new modules must :ref:`support Python 2.6+ and Python 3.5+ `. If this is an issue, please contact us (see the "Speak to us" section later in this document to learn how). * Have a look at the existing modules and how they've been named in the :ref:`all_modules`, especially in the same functional area (such as cloud, networking, databases). * Shared code can be placed into ``lib/ansible/module_utils/`` * Shared documentation (for example describing common arguments) can be placed in ``lib/ansible/plugins/doc_fragments/``.