-
SummaryAnsible lint 6.9.1 is failing in Homebrew due to using a different Python than Ansible itself
Issue Type
OS / ENVIRONMENT$ uname -a
Darwin JoR-mbp 21.6.0 Darwin Kernel Version 21.6.0: Thu Sep 29 20:13:56 PDT 2022; root:xnu-8020.240.7~1/RELEASE_ARM64_T6000 arm64
$ ansible-lint --version
ansible-lint 6.9.1 using ansible 2.13.6
STEPS TO REPRODUCE$ brew install ansible ansible-lint
...
$ ansible-lint
Traceback (most recent call last):
File "/opt/homebrew/bin/ansible-lint", line 8, in <module>
sys.exit(_run_cli_entrypoint())
^^^^^^^^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/ansible-lint/6.9.1/libexec/lib/python3.11/site-packages/ansiblelint/__main__.py", line 347, in _run_cli_entrypoint
sys.exit(main(sys.argv))
^^^^^^^^^^^^^^
File "/opt/homebrew/Cellar/ansible-lint/6.9.1/libexec/lib/python3.11/site-packages/ansiblelint/__main__.py", line 228, in main
from ansiblelint.rules import RulesCollection
File "/opt/homebrew/Cellar/ansible-lint/6.9.1/libexec/lib/python3.11/site-packages/ansiblelint/rules/__init__.py", line 19, in <module>
import ansiblelint.utils
File "/opt/homebrew/Cellar/ansible-lint/6.9.1/libexec/lib/python3.11/site-packages/ansiblelint/utils.py", line 37, in <module>
from ansible.errors import AnsibleError, AnsibleParserError
ModuleNotFoundError: No module named 'ansible' Desired BehaviorIt should work 😁 Actual Behavior
I suspect this is because ansible-lint is using Python 3.11 while ansible is still using Python 3.10:
|
Beta Was this translation helpful? Give feedback.
Answered by
ssbarnea
Dec 9, 2022
Replies: 1 comment
-
We support only the installation or distribution methods mentioned in our documentation, for anything else please contact the repackagers. Please do not raise bugs upstream for downstream issues. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
ssbarnea
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We support only the installation or distribution methods mentioned in our documentation, for anything else please contact the repackagers. Please do not raise bugs upstream for downstream issues.