On Mar 28, 9:32 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Thu, Mar 27, 2008 at 3:13 PM, Michael Wieher <[EMAIL PROTECTED]> > wrote: > > > but this is the error message. > > > >ImportError: No module named django > > > shouldn't that mean that python can't find the django module? regardless > > of if he has further issues, modules within modules or anything, if python > > can't find the initial django module that means a bad install? > > It means python running under apache can't find django. However the dev > server works, so django is there. Which leads me to suspect a permissions > problem. I know nothing of CentOS but from googling a bit it sounds like it > is a distrib possibly based off of SELinux (security-enhanced). Is django > actually installed under site-packages or is it just linked there? If it's > only linked, and the link is to some user-owned space, then probably the > issue is that apache doesn't have the access rights to read that space. > Search the list for SELinux and you'll get some hits for other people who > have tacked this problem and figured out how to set things up so apache > could read their files.
Since mod_wsgi shares many of the same issues as mod_python, you may want to also read the issues documents for mod_wsgi: http://code.google.com/p/modwsgi/wiki/ApplicationIssues In particular those sections dealing with Access Rights of Apache User and Secure Variants of UNIX. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
