I believe this is the OS's requirement, not Plesk's. Plesk itself has no python parts and AFAIK uses mod_python to enable python for customer's sites.
If you are, ie., using CentOS/RHEL 5.x, than stock python version is 2.4 and that's hard to upgrade due to some core systems depending on it, such as yum. Apache's mod_python is also built for the stock OS version of python, although I guess one could rip that out and build against something else. In this case, Plesk would use that instead. But it's not a clean solution. Regards On Monday, January 23, 2012 10:09:31 AM UTC+1, peter wrote: > > The problem I found was that Plesk requires python 2.4 and Web2py > requires at least python 2.5. So one has to install python 2.5 or > higher (I use 2.6), and use this in parallel with the python 2.4. I > could get web2py working with the rocket server. I never did get it > working with Apache so I will be interested in your results. I > currently use uwsgi on its own. This means the static directory is > served through web2py but is otherwise fast. A better route would be > nginx and uwsgi, which will work but on my system there are still > issues to resolve. > > Good luck, keep us informed of your progress > Thanks > Peter >
