Python hasn't worked for a while on my systems. The one I was just working 
on is Mystic Linux/64. It's Ubuntu 20.04.2 LTS with v1.12 A47 Linux/64 
Compiled 2021/02/12 18:33:53. I've noticed g00r00 tried to make # do the
python path for a theme, I believe the current theme. That doesn't seem
to work, but maybe I don't understand how to use it. I've found the only
thing that really works is the full path. Doing:
ldconfig -p | grep libpython
Yields:
libpython3.8.so.1.0 (libc6,x86-64) => /lib/x86_64-linux-gnu/libpython3.8.so.1.0
libpython2.7.so.1.0 (libc6,x86-64) => /lib/x86_64-linux-gnu/libpython2.7.so.1.0
whereis python yields:
python: /usr/bin/python2.7 /usr/bin/python /usr/bin/python3.8 
/usr/lib/python2.7 /usr/lib/python3.9 /usr/lib/python3.8 /etc/python2.7 
/etc/python3.8 /usr/local/lib/python2.7 /usr/local/lib/python3.8 
/usr/include/python3.8 /usr/share/python
I have the two python test scripts in /mystic/themes/default/scripts and
they are using that full path. Both being the original one and the newer one.
Running either yeilds:
Cannot initialize Python, press a key

Things look pretty standard placement wise so why don't they work? They both 
did on the earilier system before Windows10 crashed and I replaced it with 
Ubuntu 20.04.2 LTS so it's likely that. I think things last worked under
16.04 LTS, not sure about 18.04 LTS (which I had to compile 2.7).