Re: ImportError: No module named django.core.wsgi even if sys.path contains my virtualenv

2013-10-28 Thread Timothy W. Cook
Al I know is that I can run Django from a virtualenv using the development server. I have to disable SELinux to get Apache to run my Django app via WSGI. I am sure there are settings that you can make (have made) to SELinux to allow access but I have not studied it to find out what they are.

Re: ImportError: No module named django.core.wsgi even if sys.path contains my virtualenv

2013-10-28 Thread G. Allegri
Hi Timothy, I'm on a managed server, so I cannot do system changes that would require reboot. Anyway, setenforce says that SELinux is disabled (even setenforce 1). Do you think it is SELinux to block Python module loading? If I activate my virtualenv from shell I can load Django. giovanni 2013

Re: ImportError: No module named django.core.wsgi even if sys.path contains my virtualenv

2013-10-28 Thread Timothy W. Cook
CentOS is a bit of a PITA. Because it is so secure. Try turning off SELinux http://www.centos.org/docs/5/html/5.2/Deployment_Guide/sec-sel-enable-disable.html To test this out from the commandline: $setenforce 0 How to actually make it work WITH SELinux? I haven't figured that out yet. HTH,

ImportError: No module named django.core.wsgi even if sys.path contains my virtualenv

2013-10-28 Thread Giovanni Allegri
I'm getting mad with this error. I've setup Apache and wsgi configuration as usual, but this time I'm on CentOS instead of Debian, and I don't know it very well. Anyway, I tried all the ways to give mod_wsgi the chance to peak from my virtualenv libraries, both setting them with python-path argum