Comments on: Setup Python 2.5, mod_wsgi, and Django 1.0 on CentOS 5 (cPanel)

By: Venky

Venky — Sat, 20 Feb 2010 10:44:16 +0000

Nice Post, I have a similar Post at:

http://www.venkysblog.com/2009/12/centos-python...

By: Setup Python 2.6.4, mod_wsgi 2.6, and Django 1.1.1 on CentOS 5.3 (cPanel) | Perplexed Labs

Sun, 15 Nov 2009 20:37:40 +0000

[...] This is an update to my previous how-to Setup Python 2.5, mod_wsgi, and Django 1.0 on CentOS 5 (cPanel). [...]

By: WordPress to Django+PostgreSQL, part 3: Installing Apache, Python 2.6, psycopg2, and mod_wsgi

Sat, 17 Oct 2009 23:09:42 +0000

[...] a solution exists: Doing a parallel installation of Python. I’m deeply indebted to this posting from Perplexed Labs for guidance on the [...]

By: alex_davies

alex_davies — Thu, 17 Sep 2009 20:32:52 +0000

On RHEL5/CentOS5 you need to install zlib-devel and compile python 2.5 with it, i.e.

./configure –prefix=/opt/python2.5 –with-threads –enable-shared –with-zlib=/usr/include

Otherwise you can't install setuptools.

Alex

By: alex_davies

alex_davies — Thu, 17 Sep 2009 16:32:52 +0000

On RHEL5/CentOS5 you need to install zlib-devel and compile python 2.5 with it, i.e.

./configure –prefix=/opt/python2.5 –with-threads –enable-shared –with-zlib=/usr/include

Otherwise you can't install setuptools.

Alex

By: peter

peter — Sat, 29 Aug 2009 15:16:15 +0000

A really really really big thank you! This probably saved me one day++ of work.
-Peter

By: Llanilek

Llanilek — Mon, 24 Aug 2009 11:24:18 +0000

I've been looking around for something like this for ages…

only problems i've been running into is even though we give alias to python2.5 django still seems to be picking up python2.4 as default… which is really strange.

also it would be nice to explain how to get a single install of django to run rather than having to install multiple django-trunks on each account.

By: links for 2009-08-05 « Object neo = neo Object

links for 2009-08-05 « Object neo = neo Object — Thu, 06 Aug 2009 04:30:51 +0000

[...] Setup Python 2.5, mod_wsgi, and Django 1.0 on CentOS 5 (cPanel) | Perplexed Labs (tags: python centos) This entry was written by bairos, posted on August 6, 2009 at 1:30 am, filed under delicious-daily. Bookmark the permalink. Follow any comments here with the RSS feed for this post. Post a comment or leave a trackback: Trackback URL. « links for 2009-08-02 [...]

By: grahamd

grahamd — Tue, 04 Aug 2009 23:06:23 +0000

FWIW, broken ErrorDocument directives aren't likely because of running a WSGI application, it is probably because of how you defined where the error documents live. The same issue will apply with any system where you mount it on root of web server.

What you shouldn't do is put error documents in normal static document root, with no other configuration, as application mounted at root will take precedence. To expose error documents again, you need to use Alias directive to map the the error documents at the explicit URL mentioned in ErrorDocument directive. Use of Alias directive will take precedence over application mounted at root and so will still be found.

By: Seth

Seth — Wed, 29 Jul 2009 00:11:20 +0000

Nick,

SELinux is a security & permissions manager. Disabling it entirely is not recommended. You should instead become familiar enough with its settings to be able to tell it how to give your WSGI environment access to the necessary Python libs.

Running something like: "restorecon -R -v /opt/python2.5/lib" might do the trick (although this also might not be an entirely foolproof solution).

Cheers!
Seth