linting and testing virtualenv

Issue Type

• Bug report

Molecule and Ansible details

[user@host dir]$ pipenv run ansible --version
ansible 2.7.8
  config file = None
  configured module search path = ['/Users/user/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/user/.local/share/virtualenvs/project_name-F5AQQX11/lib/python3.7/site-packages/ansible
  executable location = /Users/ccuming/.local/share/virtualenvs/project_name-F5AQQX11/bin/ansible
  python version = 3.7.2 (default, Feb 12 2019, 08:15:36) [Clang 10.0.0 (clang-1000.11.45.5)]
[user@host dir]$ pipenv run molecule --version
molecule, version 2.19.0

Molecule installation method (one of):

• pipenv

Ansible installation method (one of):

• pipenv

Detail any linters or test runners used:

Desired Behavior

when i run molecule tests, i’d like the virtualenv’s packages (ansible and molecule) to not be scanned.

Actual Behaviour

when i run molecule tests, the virtualenv packages are being scanned via flake8 and testinfra.

Include a minimum complete verifiable example with output of running molecule --debug.

Pipfile

[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]

[packages]
ansible = "*"
molecule = "*"
docker-py = "*"

[requires]
python_version = "3.7"

molcule_debug.log

i tried passing exclude=*/virtualenvs/* to flake8, but that didn’t quite get it. is there something else i can try?

[decentral1se]

i’m not stepping into that flame war

You’ve already put one foot in the door … good luck!

[ssbarnea]

This seems as an unsupported use-case so I will be closing. Still, if you find a way to avoid it, you are welcomed to make a PR.