Obviously answers are possible. The trick is to set up the entire stack in an alternate location on the main machine.
So altinstall python, then easy_intall, then pip. Here is the history of the teams in my journal.
cd mkdir installations cd installations/ curl -O https://www.python.org/ftp/python/2.7/Python-2.7.tar.bz2 tar xjf Python-2.7.tar.bz2 cd Python-2.7 mkdir -p ~/usr/local make altinstall prefix=~/usr/local exec-prefix=~/usr/local ~/usr/local/bin/python2.7 -V ln -s ~/usr/local/bin/python2.7 ~/usr/local/bin/python echo "export $PATH=~/usr/local/bin:$PATH" >> ~/.bashrc source ~/.bashrc cd mkdir virtualenv cd virtualenv/ curl -O https://raw.github.com/pypa/virtualenv/master/virtualenv.py mkdir ~/envs python virtual-python.py --prefix=~/env/aws curl -O http://peak.telecommunity.com/dist/ez_setup.py ~/env/aws/bin/python ez_setup.py echo "export $PATH=~/env/aws/bin:~/usr/local/bin:$PATH" >> ~/.bashrc source ~/.bashrc easy_install virtualenv virtualenv --no-site-packages ~/env/awscli source ~/env/awscli/bin/activate pip -V pip install awscli
These are useful links that I have followed to help me achieve this goal.
Install Python in an alternate location
Install Python stack without root privileges
Devy source share