• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Upgrade from python 2.4.3 to 2.5.1 Plesk 8.2

M

muffinresearch

Guest
I have compiled and installed python 2.5.1 from source on FC4 64bit and have compiled mod_python however before I run make_install I wondered has anyone done this and does anything break in Plesk?
 
hi thanks for your reply; are you saying you've done this and it worked fine? Sorry it's not clear from your reply.
 
sorry, but i didn't do this
but never heart about issues about this case;
 
You have to install new python separately in different directory than original python (because original is used by yum/rpm) and then recompile mod_python with new python path.
 
Yes, you don't want to overwrite the existing python with 2.5. It will break a great many things, since the vast majority of internal configuration tools are python based.
 
Back
Top