This is how you can configure mod_wsgi to use Python2.7
I happened to face this same issue. And I was looking at the option on uninstalling mod_wsgi and re-installing it with appropriate configs.
Reading one of the articles I realized there was no need to un-install my current mod_wsgi and I could just go ahead and re-install mod_wsgi3.4 (earlier i had v3.2) with the settings to use Python2.7 (seems like the installation process re-writes everything without any errors/conflicts).
Since I already had Python2.7 installed.
I reinstalled mod_wsgi-3.4 (without performing any un-installations)
[root@server ~]# cd ~
[root@server ~]# wget http://modwsgi.googlecode.com/files/mod_wsgi-3.4.tar.gz
[root@server ~]# tar xvf mod_wsgi-3.4.tar.gz
[root@server ~]# cd mod_wsgi-3.4
Configured mod_wsgi with the installed python2.7
[root@server ~]#./configure --with-python=/usr/local/bin/python2.7
[root@server ~]# make
[root@server ~]# make install
The below two commands are very important. Replace /usr/local/lib with the folder where you have installed libpython2.7.so.1.0 if it is not in /usr/local/lib.
[root@server ~]# LD_LIBRARY_PATH=/usr/local/lib /usr/local/bin/python
[root@server ~]# ldconfig
Restart Apache Server
[root@server ~]# service httpd restart
[root@server ~]# ldd /etc/httpd/modules/mod_wsgi.so
Output of the above command:Line2 indicates that your mod_wsgi is now using Python2.7 libraries. YAY!
linux-vdso.so.1 => (0x00007fffc0aa9000)
libpython2.7.so.1.0 => /usr/lib/libpython2.7.so.1.0 (0x00007f03a5b20000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f03a5903000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f03a56fe000)
libutil.so.1 => /lib64/libutil.so.1 (0x00007f03a54fb000)
libm.so.6 => /lib64/libm.so.6 (0x00007f03a5277000)
libc.so.6 => /lib64/libc.so.6 (0x00007f03a4ee2000)