On Fri, Mar 28, 2008 at 11:45 PM, Graham Dumpleton <[EMAIL PROTECTED]> wrote: > > On Mar 29, 5:04 am, Slayer_X <[EMAIL PROTECTED]> wrote: > > Problem solved! > > > > I deleted the symlinks, delete de django-trunk dir and make a fresh > > install directly in > > > > /usr/lib/python2.4/site-packages/django > > What do you mean by 'make a fresh install directly in'? Do you mean > you copied it in by hand or did you use an appropriate setup.py file > script? >
We were chatting on #django-es when César solved this. What he means when he says a fresh install is that he removed the django symlink from /usr/lib/python2.4/site-packages/ (that pointed to a Django SVN WC on his home dir) Then, as root, he did a cd /usr/lib/python2.4/site-packages/ svn co http://code.djangoproject.com/svn/django/trunk/django The problem he was having with the symlink approach was related to the fact that, even when he theoretically disabled SElinux and rebooted, something wasn´t working when mod_python wanted to import django (importing django in a normal user interactive python session worked ok.) > > > In my Apache conf I use this path > > > > PythonPath "['/'] + sys.path" > > Why are you adding '/' to the module search path. There shouldn't be > any need to add the root of the file system to it. > This is because his project was located in a dir below / as in: / ripsol/ settings.py urls.spy ... -- Ramiro Morales --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
