New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drawing your attention to problems with dopy 0.3.7 on Mac OS X #41

Open
davidjpeacock opened this Issue Jan 22, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@snoopdouglas

This comment has been minimized.

Show comment
Hide comment
@snoopdouglas

snoopdouglas May 5, 2016

+1, still an issue for me.

From comments on ansible/ansible-modules-core#2509 - here's a temporary solution:

  • In Ansible hosts, append to localhost entry: localhost ansible_python_interpreter=python
  • pip install six
  • pip install 'dopy>=0.3.5,<=0.3.5'

+1, still an issue for me.

From comments on ansible/ansible-modules-core#2509 - here's a temporary solution:

  • In Ansible hosts, append to localhost entry: localhost ansible_python_interpreter=python
  • pip install six
  • pip install 'dopy>=0.3.5,<=0.3.5'
@regentgal

This comment has been minimized.

Show comment
Hide comment
@regentgal

regentgal May 12, 2016

Contributor

This issue was resolved for me by upgrading to ansible 2.0.2.

Contributor

regentgal commented May 12, 2016

This issue was resolved for me by upgrading to ansible 2.0.2.

@snoopdouglas

This comment has been minimized.

Show comment
Hide comment
@snoopdouglas

snoopdouglas May 14, 2016

@regentgal Running 2.0.2.0 here :(

@regentgal Running 2.0.2.0 here :(

@kontrafiktion

This comment has been minimized.

Show comment
Hide comment
@kontrafiktion

kontrafiktion Jul 6, 2016

Collaborator

Is this really a dopy issue? I have the same basic problem with dopy 0.3.5 (just with another error message). The basic problem as far as I can say is this: Ansible uses /opt/bin/python unless explicitly configured to use another Python interpreter. So even if you are running Ansible itself with another Python, when connecting (even to localhost) Ansible uses /opt/bin/python.
Now the question becomes: "where" did you install dopy? In the import path for /usr/bin/python or in the import path for the Python you are using to start Ansible?

I just confirmed this by printing sys.executable from inside the digital_ocean Ansible module.
Without setting ansible_python_interpreter the Python used was /opt/bin/python and I hadn't installed dopy into its import path.

So please check, which Python are using? Mine is either in a virtualenv or at /usr/local/bin (installed via HomeBrew)

Collaborator

kontrafiktion commented Jul 6, 2016

Is this really a dopy issue? I have the same basic problem with dopy 0.3.5 (just with another error message). The basic problem as far as I can say is this: Ansible uses /opt/bin/python unless explicitly configured to use another Python interpreter. So even if you are running Ansible itself with another Python, when connecting (even to localhost) Ansible uses /opt/bin/python.
Now the question becomes: "where" did you install dopy? In the import path for /usr/bin/python or in the import path for the Python you are using to start Ansible?

I just confirmed this by printing sys.executable from inside the digital_ocean Ansible module.
Without setting ansible_python_interpreter the Python used was /opt/bin/python and I hadn't installed dopy into its import path.

So please check, which Python are using? Mine is either in a virtualenv or at /usr/local/bin (installed via HomeBrew)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment