I ended up going down the virtualenv path for this. Covers OSX as well as 
Linux. I went this path in order to have the ability to switch back and 
forth between versions in order to test functionality between 1.9.x and 2.0

http://everythingshouldbevirtual.com/ansible-setting-up-an-ansible-control-machine-part-1


On Friday, January 15, 2016 at 11:29:58 AM UTC-5, Slim Slam wrote:
>
> As you may recall, I had to uninstall Ansible 1.9.4 in order to install 
> Ansible 2.0.0.0. But now, upgrading to Ansible 2.0.0.2 succeeds but has no 
> effect.
> I'm on MacOSX El Capitan (10.11.2)
>
> $ ansible --version
> ansible 2.0.0.0
>   config file =
>   configured module search path = Default w/o overrides
> $
>
> $ sudo -H pip install --upgrade ansible --user python
> Password:
> Collecting ansible
>   Downloading ansible-2.0.0.2.tar.gz (1.5MB)
>     100% |################################| 1.5MB 258kB/s
> Requirement already up-to-date: python in /System/Library/Frameworks/
> Python.framework/Versions/2.7/lib/python2.7/lib-dynload
> Requirement already up-to-date: paramiko in /Library/Python/2.7/site-packages 
> (from ansible)
> Requirement already up-to-date: jinja2 in /Library/Python/2.7/site-packages 
> (from ansible)
> Requirement already up-to-date: PyYAML in /Library/Python/2.7/site-packages 
> (from ansible)
> Collecting setuptools (from ansible)
>   Using cached setuptools-19.2-py2.py3-none-any.whl
> Requirement already up-to-date: pycrypto>=2.6 in 
> /Library/Python/2.7/site-packages 
> (from ansible)
> Requirement already up-to-date: ecdsa>=0.11 in 
> /Library/Python/2.7/site-packages 
> (from paramiko->ansible)
> Requirement already up-to-date: MarkupSafe in 
> /Library/Python/2.7/site-packages 
> (from jinja2->ansible)
> Installing collected packages: setuptools, ansible
>   Running setup.py install for ansible
> Successfully installed ansible-2.0.0.2 setuptools-1.1.6
> $
>
>
> $ ansible --version
> ansible 2.0.0.0
>   config file =
>   configured module search path = Default w/o overrides
> $
>
> What is the correct way to handle updates going forward?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/d1e67b8b-82ff-4f55-9f94-5eb6b1d6209f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to