I had a hard time finding what I would consider an official means. If you want to install Python 3.3, in my case because various Openstack projects that maintain 3.3 compatibility. What is causing this? It doesn't happen if I do not upgrade but leave Python at 2.7.Ubuntu 14.04 by default uses Python 2.7 and 3.4. Is this assumption wrong? I'm a bit confused about this, as I guess that the python-dev in the repo is based on 2.7.6, if that makes any sense.Īdditionally, since I'm running pip in a virtualenv, when issuing pip install -upgrade -force-reinstall pyopenssl in there I do get a OSError: Permission denied: '/usr/local/lib/python2.7/dist-packages/pyOpenSSL-0.15.1.dist-info' error, which is most likely because I'm not running sudo (but as the default user), in order for the library to get installed into the virtualenv.

How do I deal with other libraries, like pip install -upgrade -force-reinstall pyopenssl, which compiles some C code? In order for the C code to get compiled, I need to sudo apt-get install python-dev in order to get the headers.

Should I stick to make altinstall? How do I make that my default python then? make altinstall is therefore recommended instead of make install since it only installs exec_prefix/bin/pythonversion. Warning: make install can overwrite or masquerade the python binary. I use make install instead of sudo make altinstall because I want it to be the only Python 2.7 on the system, the default one. Ubuntu 14.04 from AWS ships with python 2.7.6.īefore doing anything else to the image, I do an upgrade to 2.7.10 by issuing sudo apt-get -y install build-essential checkinstall libreadline-gplv2-dev libncursesw5-dev libssl-dev libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev

Install python 2.7 ubuntu 14.04