cmueller/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

This was changed to python 2.7 but should have remained python 2.6 (#66836)

Browse source 
* Modules are still python-2.6+ unless there's a compelling reason not
  to be.
This commit is contained in:
Toshio Kuratomi 2020-01-28 07:32:03 -08:00 committed by Alicia Cozine
parent 5ff899662d
commit abc8b0ae73
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/docsite/rst/dev_guide/developing_modules_checklist.rst
View file

@ -16,7 +16,7 @@ To contribute a module to Ansible, you must:
* write your module in either Python or Powershell for Windows * write your module in either Python or Powershell for Windows
* use the ``AnsibleModule`` common code * 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 <developing_python_3>` * use proper :ref:`Python 3 syntax <developing_python_3>`
* follow `PEP 8 <https://www.python.org/dev/peps/pep-0008/>`_ Python style conventions - see :ref:`testing_pep8` for more information * follow `PEP 8 <https://www.python.org/dev/peps/pep-0008/>`_ Python style conventions - see :ref:`testing_pep8` for more information
* license your module under the GPL license (GPLv3 or later) * license your module under the GPL license (GPLv3 or later)

2
docs/docsite/rst/dev_guide/developing_modules_in_groups.rst
View file

@ -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`. * 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. * 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+ <developing_python_3>`. 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+ <developing_python_3>`. 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). * 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 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/``. * Shared documentation (for example describing common arguments) can be placed in ``lib/ansible/plugins/doc_fragments/``.