Run from source hacking script broken?

Archives Ansible Developer
1

I followed the instructions here: http://docs.ansible.com/ansible/intro_installation.html#running-from-source

However when I run ansible from the newly cloned repo, I get the following error:

mpetrive@mpetrive-laptop ~/sandbox/ansible $ ansible -v
Traceback (most recent call last):
File “/home/mpetrive/sandbox/ansible_fresh/bin/ansible”, line 39, in
from ansible.errors import AnsibleError, AnsibleOptionsError, AnsibleParserError
ImportError: cannot import name AnsibleOptionsError

Any idea what the issue is?

2

probably mixing 1.9 and 2.0 files, `make clean` should get rid of any
files not of the current branch, use that before using the env-setup
script again.

3

I did a ‘make clean’ and this doesn’t fix the issue. Again this a clean checkout into a new directory. I should have mentioned I do have 1.9.4 installed on my machine. Could that be causing the issue?

4

probably

5

We have seen some scenarios where easy_install (and modules installed with easy_install) created an easy-install.pth file that was causing the PYTHONPATH to get paths inserted in front of those created by the hacking script.

As such, it would end up importing files from other ansible installations.

After running the hacking script, if you run the following command, it should show you those search directories:

python -c ‘import sys; print sys.path’

If you see any site-packages, dist-packages, or maybe .egg paths before the ansible source directories, this is likely the cause.