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-p
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
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
In my Apache conf I use this path
PythonPath "['/'] + sys.path"
And now Django is working :-D
Thanks a lot for your help
César
PD: Sorry for my ba
Hi everyone!
> Michael Wieher wrote:
> Get rid of your installation of django and re-install it.
---
done
>To test it, go to any unrelated location in your file-system (ie: cd /usr
>or cd /var or something, start up python and import django.)
---
I can import django without errors
>Also, be su
Hi everyone!
> Michael Wieher wrote:
> Get rid of your installation of django and re-install it.
---
done
>To test it, go to any unrelated location in your file-system (ie: cd /usr
>or cd /var or something, start up python and import django.)
---
I can import django without errors
>Also, be su
Hi everyone!
> Michael Wieher wrote:
> Get rid of your installation of django and re-install it.
---
done
>To test it, go to any unrelated location in your file-system (ie: cd /usr
>or cd /var or something, start up python and import django.)
---
I can import django without errors
>Also, be su
Slayer_X wrote:
> # vim /etc/httpd/conf/httpd.conf
>
> PythonPath "['/usr/lib/python2.4/site-packages/django'] +
> sys.path"
> SetHandler python-program
> PythonHandler django.core.handlers.modpython
> PythonDebug On
> SetEnv DJANGO_SETTINGS_MODULE ripsol.settings
>
Try this
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? regardle
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 p
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?
--~--~-
> If your python interpreter can't import django, you installed it
> wrong.
> C'est tres facil.
One of the previous post in this thread mentions the development
server works fine, so django can be imported from the shell
apparently. But testing that will never hurt; there may happen to be a
Look.
If your python interpreter can't import django, you installed it wrong.
C'est tres facil.
the django module should be installed to the system and should be importable
from anywhere. Setting your PYTHON_PATH is, at best, a hack, and at worst,
will cause massive problems (as hacks do) when an
Hi, sorry for the delay
On Mar 16, 2:45 pm, prz <[EMAIL PROTECTED]> wrote:
> are you sure you have django directory _IN_
>
> /usr/lib/python2.4/site-packages/django
Yes, I have the django directory
> or is it only
>
> /usr/lib/python2.4/site-packages/django/core/handlers/modpython.py
--
I have
13 matches
Mail list logo
