HOWTO install a newer (or older) version of Python

sean

ngkabra I tried Python-3.10.0rc1 and the make step gave the following warning at the end:

Could not build the ssl module!
Python requires a OpenSSL 1.1.1 or newer

It's happening because the OpenSSL in CentOS7 is too old.

To work around that you'll need to build your own OpenSSL from source and then use the various "with-openssl" configure options to point your install at that.

ngkabra

sean Thanks Sean,
I built my own openssl. If anyone else runs into this problem, this is what I did (Note: replace navin with your own username)

$ mkdir src && cd src && wget <openssl-url> && cd <openssl-directory>
$ ./config --prefix=/home/navin/opt/ssl --openssldir=/home/navin/opt/ssl && make && make install

Now install python:

$ cd src && wget <python-url> && cd <python-directory>
$ ./configure --prefix=/home/navin/opt --with-openssl=/home/navin/opt/ssl --with-openssl-rpath=auto && make && make install

This made everything work.

ngkabra

Also, if anyone is experimenting with python3.10, don't bother yet. As far as I can tell uwsgi does not yet support python3.10. As a result, although I got python3.10 working successfully, I couldn't actually get my app running because no uwsgi.

sean

ngkabra I've tested this and had no problems installing and running uwsgi on Python 3.10.

karol

sean When I follow this instruction and create an env with the bespoke python version, the pip inside the env is not tied to the python I just downloaded. If I try python -m pip --version it says pip cannot be found. Any ideas?

sean

karol pip should be installed by default on any new virtual environment.

If it's not working then first check to ensure that you have the correct environment activated, then run python -m ensurepip upgrade to install pip.

karol

sean

It doesn't seem to work the way you say. This env was created earlier using python 3.3.7. I want it because it's the highest version Django 1.6 supports.

[karol@opal4 apps]$ cd django_16_python3/
[karol@opal4 django_16_python3]$ source env/bin/activate 
(env) [karol@opal4 django_16_python3]$ python --version
Python 3.3.7
(env) [karol@opal4 django_16_python3]$ pip --version 
pip 21.3.1 from /usr/local/lib/python3.6/site-packages/pip (python 3.6)
(env) [karol@opal4 django_16_python3]$ # not what I hoped for ^
(env) [karol@opal4 django_16_python3]$ python -m ensurepip upgrade
/home/karol/apps/django_16_python3/env/bin/python: No module named ensurepip

sean

karol in that case please try to install pip by following the get-pip.py instructions at:

https://pip.pypa.io/en/stable/installation/#get-pip-py

etienneh

In case anyone wants compressed instructions, here's some using pyenv. There's been no new version of 1.1 since 2018 so these commands should be stable and portable across users.

mkdir -p $HOME/opt/
mkdir -p $HOME/tmp/pyenv-builds/

cd ~/tmp
export OPENSSL_VER=1.1.1s
wget https://www.openssl.org/source/openssl-$OPENSSL_VER.tar.gz
tar -xvf openssl-$OPENSSL_VER.tar.gz
rm -rf openssl-$OPENSSL_VER.tar.gz
mv openssl-$OPENSSL_VER openssl
cd openssl

./config --prefix=$HOME/opt/ssl --openssldir=$HOME/opt/ssl
make
make install

env TMPDIR=$HOME/tmp/pyenv-builds CONFIGURE_OPTS="-with-openssl=$HOME/opt/ssl -with-openssl-rpath=auto" pyenv install 3.10.X

stefan

Regarding the first message in this thread:

Note: the following Python versions are pre-installed on all Opalstack servers: 2.7, 3.6, 3.10, 3.11, 3.12, 3.13

I'm looking at opal6 and the only python versions I'm seeing in /usr/bin/ are 2.7, 3.4 and 3.6. What am I missing?

I'd rather not have to manage newer python versions myself if possible, although I did that in the past and I know it's not that hard.

Ștefan

sean

stefan the other Pythons are in /usr/local/bin:

/usr/local/bin/python3.10
/usr/local/bin/python3.11
/usr/local/bin/python3.12
/usr/local/bin/python3.13

« Previous Page