How to Install Python 2.7 on CentOS/RHEL 9/8 and Fedora

Please note that the command
curl “https://bootstrap.pypa.io/get-pip.py” -o “get-pip.py”
does not work anymore. User gets error
curl: (35) Peer reports incompatible or unsupported protocol version.
I think this error is given by the fact that the site “https://bootstrap.pypa.io/get-pip.py” does not accept TLS version older than 1.2.
Workaround was to give the command on a different machine that had TLS1.2 and copy the downloaded get-pip.py file from that machine to the CentOS machine on location /usr/src/Python-2.7.16
after this step, give the last command from the webBlog.
python2.7 get-pip.py

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won’t btained after that date. A future version of pip will drop support for Python 2.7.

WHAT? when i type python -V im still on 2.6 then it say that

>>> import boto
>>> boto.version
Traceback (most recent call last):
File “”, line 1, in
AttributeError: ‘module’ object has no attribute ‘version’
>>>

how to fix this error

Im getting this error, is there any way to bypass certificate checking?

[root@localhost Python-2.7.15]# python2.7 get-pip.py
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won’t be maintained after that date. A future version of pip will drop support for Python 2.7.
Collecting pip
Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)’),)’: /simple/pip/
Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)’),)’: /simple/pip/
Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)’),)’: /simple/pip/
Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)’),)’: /simple/pip/
Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by ‘SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)’),)’: /simple/pip/
Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host=’pypi.org’, port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)’),)) – skipping
Could not find a version that satisfies the requirement pip (from versions: )
No matching distribution found for pip
Could not fetch URL https://pypi.org/simple/pip/: There was a problem confirming the ssl certificate: HTTPSConnectionPool(host=’pypi.org’, port=443): Max retries exceeded with url: /simple/pip/ (Caused by SSLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618)’),)) – skipping

Two additions:

1. altinstall role is not properly described. Altinstall means “don’t overwrite $PREFIX/bin/python symlink”; in our case system-default Python is installed under /usr/bin/python (PREFIX=/usr), while we install 2.7.14 Python under /usr/local/bin/python (PREFIX=/usr/local).
So if we use `make install` then we will create `/usr/local/bin/python`, without overwriting `/usr/bin/python`. And `/usr/local/bin` has higher priority than `/usr/bin` resulting in new Python version being used for `python` command, and this may break some system-wide stuff. Although scripts with hard-coded `#!/usr/bin/python` in shebang will still use old python version.

2. No need to download `get-pip.py` script because Python 2.7.14 has built-in `ensurepip` module. It is enough to enter `python2.7 -m ensurepip` to install pip.

All worked and many thanks for publishing this!

python2.7 is not a valid command

/usr/local/bin/python2.7 –version ,This path need to be added to PATH

/usr/local/bin/python2.7 –version

I am getting error in the last command python2.7 get-pip.py
The following is the error msg
[uexcel@localhost Python-2.7.13]$ python2.7 get-pip.py
Collecting pip
Using cached pip-9.0.1-py2.py3-none-any.whl
Collecting wheel
Using cached wheel-0.29.0-py2.py3-none-any.whl
Installing collected packages: pip, wheel
Exception:
Traceback (most recent call last):
File “/tmp/tmpGCg2kV/pip.zip/pip/basecommand.py”, line 215, in main
status = self.run(options, args)
File “/tmp/tmpGCg2kV/pip.zip/pip/commands/install.py”, line 342, in run
prefix=options.prefix_path,
File “/tmp/tmpGCg2kV/pip.zip/pip/req/req_set.py”, line 784, in install
**kwargs
File “/tmp/tmpGCg2kV/pip.zip/pip/req/req_install.py”, line 851, in install
self.move_wheel_files(self.source_dir, root=root, prefix=prefix)
File “/tmp/tmpGCg2kV/pip.zip/pip/req/req_install.py”, line 1064, in move_wheel_files
isolated=self.isolated,
File “/tmp/tmpGCg2kV/pip.zip/pip/wheel.py”, line 345, in move_wheel_files
clobber(source, lib_dir, True)
File “/tmp/tmpGCg2kV/pip.zip/pip/wheel.py”, line 316, in clobber
ensure_dir(destdir)
File “/tmp/tmpGCg2kV/pip.zip/pip/utils/__init__.py”, line 83, in ensure_dir
os.makedirs(path)
File “/usr/lib64/python2.7/os.py”, line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 13] Permission denied: ‘/usr/lib/python2.7/site-packages/pip’
[uexcel@localhost Python-2.7.13]$

I installed the version 2.7.5 but i don’t find the file python2.7. I d’ont understand.

Hi,

This works perfectly.
Could you show how to install pyodbc to this python2.7 altinstall dir?
By default running the pyodbc rpm, it gets install to the python 2.6 dir.

Please advise. thanks.

Worked as a charm for me on Centos 6.4. Thank you very for the article.

Just a heads up, if you are on centos/rhel 7, where python2.7.5 is the default, the altinstall option for any other python2.7 version (2.7.11 for instance) will break your installation as it writes to the same /usr/lib/python2.7 directory and destroys the yum modules. I am sure there is a way around this, but I just encountered this issue and it took rebuilding yum from a few RPMs just to get my system back to normal.