Re: [modwsgi] installing mod_wsgi for ucs2 python

2012-07-09 Thread Graham Dumpleton
This is occurring because you have a Python 2.7 installed in a system location as well. Why aren't you using the system Python 2.7? To get around this issue, when building Python and also mod_wsgi. Set: LD_RUN_PATH=/opt/lib export LD_RUN_PATH This only needs to be set when they are

Re: [modwsgi] installing mod_wsgi for ucs2 python

2012-07-09 Thread Alan Kesselmann
So let me get this straight so i dont do it rial and error way for 1 hour: 1) unpack 2.7.3. 2 ) LD_RUN_PATH=/opt/lib 3) export $LD_RUN_PATH 4) ./configure --enable-shared --prefix=/opt --enable-unicode=ucs2 5) make 6 ) make install? And yes - i have python 2.7.2 installed and im installing 2.7.3

Re: [modwsgi] installing mod_wsgi for ucs2 python

2012-07-09 Thread Graham Dumpleton
On 9 July 2012 18:37, Alan Kesselmann alan.kesselm...@gmail.com wrote: So let me get this straight so i dont do it rial and error way for 1 hour: 1) unpack 2.7.3. 2 ) LD_RUN_PATH=/opt/lib 3) export $LD_RUN_PATH No '$'. Just: export LD_RUN_PATH Make sure also run at this point: make

Re: [modwsgi] installing mod_wsgi for ucs2 python

2012-07-09 Thread Alan Kesselmann
Awesome! Thanks Graham! Both modules installed successfully and virtualenv too. At first apache wouldnt start but after restarting computer it works too now. This didnt fix my original problem ( http://stackoverflow.com/questions/11382024/python-version-virtualenvwrapper-and-django), but at

Re: [modwsgi] installing mod_wsgi for ucs2 python

2012-07-09 Thread Graham Dumpleton
Sort of looks like the virtual environment you are pointing mod_wsgi at was constructed using Python 2.7.2 and not Python 2.7.3. Try some of the checks starting at: http://code.google.com/p/modwsgi/wiki/CheckingYourInstallation#Python_Shared_Library Graham On 9 July 2012 20:59, Alan Kesselmann

Re: [modwsgi] installing mod_wsgi for ucs2 python

2012-07-09 Thread Alan Kesselmann
Hmmm.. ldd /opt/bin/python prints out : alan@alan:/opt/lib/python2.7$ ldd /opt/bin/python linux-vdso.so.1 = (0x7fff4818c000) libpython2.7.so.1.0 = /opt/lib/libpython2.7.so.1.0 (0x7f6bf236e000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f6bf212d000) libc.so.6 =

Re: [modwsgi] installing mod_wsgi for ucs2 python

2012-07-09 Thread Graham Dumpleton
On 9 July 2012 21:39, Alan Kesselmann alan.kesselm...@gmail.com wrote: Hmmm.. ldd /opt/bin/python prints out : alan@alan:/opt/lib/python2.7$ ldd /opt/bin/python linux-vdso.so.1 = (0x7fff4818c000) libpython2.7.so.1.0 = /opt/lib/libpython2.7.so.1.0 (0x7f6bf236e000) libpthread.so.0

Re: [modwsgi] installing mod_wsgi for ucs2 python

2012-07-09 Thread Alan Kesselmann
alan@alan:/usr/lib/apache2/modules$ ldd mod_wsgi.so linux-vdso.so.1 = (0x7fff497ff000) libpython2.7.so.1.0 = /opt/lib/libpython2.7.so.1.0 (0x7fdc404d5000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fdc40294000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6

[modwsgi] mod_wsgi under virtualenv: Error no module named site

2012-07-09 Thread RedBaron
I know this question has been asked many times and you have patiently answered it each time. But those solutions are not working for me. I have already looked at the wiki and checked my installation. I have standard python 2.6 installed on my system. I have also created a virtual environment to

Re: [modwsgi] mod_wsgi under virtualenv: Error no module named site

2012-07-09 Thread Graham Dumpleton
You are missing a WSGIProcessGroup directive to go with your WSGIDaemonProcess directive. That isn't the cause of your problem. The problem is more likely because the user that Apache runs as can't read into your /home/admin directory because there is no permission for others to read into it.

[modwsgi] Re: mod_wsgi under virtualenv: Error no module named site

2012-07-09 Thread RedBaron
Yes that was indeed the problem. My /home/admin was 700 although I had fixed permissions is /home/admin/py_run. Changing /home/admin permissions to 755 fixed it. Thanks On Jul 10, 10:32 am, Graham Dumpleton graham.dumple...@gmail.com wrote: You are missing a WSGIProcessGroup directive to go with