Awesome, Karen, that was it! Thank you so much. Here's the fix for you RHEL5 (Red Hat Enterprise Linux 5 | RHEL 5) users.
My working directory and subdirectories needed SELinux permission to be used by apache/httpd so I ran this command: [root]# chcon -R -t httpd_user_content_t /Working See my solution reference here: http://docs.fedoraproject.org/selinux-faq-fc3/index.html#id2825658 Thank you again to all that offered aid. Scott On Jan 16, 10:39 am, Scott <[EMAIL PROTECTED]> wrote: > @Graham: > It looks like it is a working django load. Also, the permissions are > the same as when they were able to load while in the python site > packages folder. > --------------- > Python 2.4.3 (#1, Dec 11 2006, 11:38:52) > [GCC 4.1.1 20061130 (Red Hat 4.1.1-43)] on linux2 > Type "help", "copyright", "credits" or "license" for more information.>>> > import django > >>> print django.__file__ > > /Working/django/django/__init__.pyc > > --------------- > > @Marty: > Here is the path to my django __init__.pyc file as output above in the > test requested by Graham: /Working/django/django/__init__.pyc > > @Karen: > This sounds promising I'm digging into that and will post my findings. > > Thank you for your responses, kind folks. > > Scott --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
