Re: manage.py setting sys.path wrong

2007-05-17 Thread birkin
On May 17, 1:22 pm, Baurzhan Ismagulov <[EMAIL PROTECTED]> wrote: ... > bash-2.05$ PYTHONPATH=/export/home/myusername/django_src python manage.py ... That's it! Thanks *very* much. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: manage.py setting sys.path wrong

2007-05-17 Thread Baurzhan Ismagulov
Hello birkin, On Thu, May 17, 2007 at 09:25:41AM -0700, birkin wrote: > bash-2.05$ python ./manage.py > Traceback (most recent call last): > File "./manage.py", line 2, in ? > from django.core.management import execute_manager > ImportError: No module named django.core.management ... > PYTH

Re: manage.py setting sys.path wrong

2007-05-17 Thread birkin
Hi all, Lukas' problem was solved thanks to your efforts, but I have the same error message that I can't figure out. Apologies for the long post; I thought the info might be useful. Thanks in advance. -Birkin -> Simple description of problem: bash-2.05$ bash-2.05$ python ./manage.py Traceback

Re: manage.py setting sys.path wrong

2007-03-29 Thread James Bennett
On 3/29/07, Lukas Kolbe <[EMAIL PROTECTED]> wrote: > Okay. I renamed my project from "site" to another name ... and voila, > everything works as expected. Yeah, that was almost certainly a conflict with the built-in Python module 'site'[1]. There are some checks in manage.py now which do their be

Re: manage.py setting sys.path wrong

2007-03-29 Thread Lukas Kolbe
Am Donnerstag, den 29.03.2007, 23:54 +1000 schrieb Malcolm Tredinnick: Okay okay, you got me there. I wondered if I missed anything and looked again at the django tutorial (which I didn't to for quite a while), and what's there? Yes, from tutorial number 1: > > You’ll need to avoid naming proje

Re: manage.py setting sys.path wrong

2007-03-29 Thread Malcolm Tredinnick
On Thu, 2007-03-29 at 14:26 +0200, Lukas Kolbe wrote: > Hi! > > I have a problem I came across for a while now. > > To start the fcgi-instance, I use manage.py as follows: > > su -c "DJANGO_DB_NAME=dbname DJANGO_DB_PASS=dbpass \ > DJANGO_DB_USER=dbuser DJANGO_SECRET_KEY=secret \ > /srv/vhos

Re: manage.py setting sys.path wrong

2007-03-29 Thread Lukas Kolbe
> On Thu, Mar 29, 2007 at 02:26:32PM +0200, Lukas Kolbe wrote: > > > > Hi! > > > > I have a problem I came across for a while now. > > > > To start the fcgi-instance, I use manage.py as follows: > > > > su -c "DJANGO_DB_NAME=dbname DJANGO_DB_PASS=dbpass \ > > DJANGO_DB_USER=dbuser DJANGO_SEC

Re: manage.py setting sys.path wrong

2007-03-29 Thread Brett Parker
On Thu, Mar 29, 2007 at 02:26:32PM +0200, Lukas Kolbe wrote: > > Hi! > > I have a problem I came across for a while now. > > To start the fcgi-instance, I use manage.py as follows: > > su -c "DJANGO_DB_NAME=dbname DJANGO_DB_PASS=dbpass \ > DJANGO_DB_USER=dbuser DJANGO_SECRET_KEY=secret \ >

manage.py setting sys.path wrong

2007-03-29 Thread Lukas Kolbe
Hi! I have a problem I came across for a while now. To start the fcgi-instance, I use manage.py as follows: su -c "DJANGO_DB_NAME=dbname DJANGO_DB_PASS=dbpass \ DJANGO_DB_USER=dbuser DJANGO_SECRET_KEY=secret \ /srv/vhosts/myhost/site/manage.py runfcgi daemonize=false \ socket=/srv/sockets