ansible/community.general
1
0
Fork 0
mirror of https://github.com/ansible-collections/community.general.git synced 2024-09-14 20:13:21 +02:00
Code Releases Activity

Update the way we make a module be tested for py3 syntax compliance

Browse source
This commit is contained in:
Toshio Kuratomi 2016-05-18 18:34:58 -07:00
parent 9c13c7b139
commit 8789cfb514
1 changed files with 11 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
docsite/rst/developing_modules_python3.rst
View file

@ -145,12 +145,15 @@ ported a module so that its syntax works with Python-3, we need to modify
.travis.yml so that the module is included in the syntax check. Here's the
relevant section of .travis.yml::
script:
env:
global:
- PY3_EXCLUDE_LIST="cloud/amazon/cloudformation.py
cloud/amazon/ec2_ami.py
[...]
- python3.4 -m compileall -fq system/ping.py
- python3.5 -m compileall -fq system/ping.py
utilities/logic/wait_for.py"
At the moment this is a whitelist. Just add your newly ported module to that
line. Eventually, not compiling on Python-3 will be the exception. When that
occurs, we will move to a blacklist for listing which modules do not compile
under Python-3.
The :envvar:`PY3_EXCLUDE_LIST` environment variable is a blacklist of modules
which should not be tested (because we know that they are older modules which
have not yet been ported to pass the Python-3 syntax checks. To get another
old module to compile with Python-3, remove the entry for it from the list.
The goal is to have the LIST be empty.