-
Notifications
You must be signed in to change notification settings - Fork 668
Closed
Description
Issue Type
- Feature request
Molecule and Ansible details
ansible 2.4.2.0
config file = /Users/dfinninger/.ansible.cfg
configured module search path = ['/Users/dfinninger/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /Users/dfinninger/.virtualenvs/infra-py3/lib/python3.6/site-packages/ansible
executable location = /Users/dfinninger/.virtualenvs/infra-py3/bin/ansible
python version = 3.6.3 (default, Oct 4 2017, 06:09:15) [GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37)]
molecule, version 2.5.0
- Molecule installation method: pip
- Ansible installation method: pip
Desired Behaviour
Ability to use Python 3
Actual Behaviour (Bug report only)
$ molecule --debug init
ERROR: Python version '3.6.3' not supported. Molecule only supports python version = 2.7.
$ molecule --no-debug init
ERROR: Python version '3.6.3' not supported. Molecule only supports python version = 2.7.
$ molecule init
ERROR: Python version '3.6.3' not supported. Molecule only supports python version = 2.7.
Additional Discussion
Is there a reason for explicitly blocking Python 3 from molecule?
It looks like the CLI code explicitly disables Python 3.6. The CHANGELOG mentions that version checks were added and the associated pull request doesn't shed much light on the decision either.
Is there a particular rationale for this? I've searched through the docs (and maybe I missed it) but I couldn't find anywhere that states why this is blocked.
#763 states that Molecule v2 is 3.5/3.6 compliant.
A note in the documentation about this or removing the constraint would be greatly appreciated. If work is needed to support Python3, then I can try to devote some cycles over the holidays.
joshuacherry, tivvit and akamalov
Metadata
Metadata
Assignees
Labels
No labels