export PYTHONPATH=/djsite/mysite
pubu...@pubuntu:~/djsite/mysite$
pubu...@pubuntu:~/djsite/mysite$
pubu...@pubuntu:~/djsite/mysite$ python manage.py runserver
Traceback (most recent call last):
File "manage.py", line 2, in <module>
from django.core.management import execute_manager
ImportError: No module named django.core.management
pubu...@pubuntu:~/djsite/mysite$
but it exists:
pubu...@pubuntu:~$
+ find -name management -print
./djsite/mysite/django-trunk/django/core/management
./djsite/mysite/django-trunk/django/contrib/auth/management
./djsite/mysite/django-trunk/django/contrib/gis/management
./djsite/mysite/django-trunk/django/contrib/sitemaps/management
./djsite/mysite/django-trunk/tests/modeltests/user_commands/management
./djsite/mysite/django-trunk/tests/regressiontests/admin_scripts/
management
Do I copy /djsite/mysite/django-trunk/django/core/management
Into /djsite/mysite
On Apr 28, 8:57 am, Karen Tracey <kmtra...@gmail.com> wrote:
> On Mon, Apr 27, 2009 at 1:30 PM, bconnors <bob.conn...@wdc.usda.gov> wrote:
>
> > With my ubuntu I can’t type @
>
> That's bizarre, but a topic for another list.
>
>
>
> > So I can’t do :
> > export PYTHONPATH=/path/to/your/django/checkout
> > to the directory I was using which was
> > pubu...@pubuntu:~/djsite/mysite$
>
> There is no @ in the path there. The format of the command prompt you see
> is:
>
> u...@machine:path$
>
> where user=login name
> machine=host name
> path=current working directory
>
> You don't need to include the u...@machine part when you export the
> PYTHONPATH, just the path part.
>
> > so I thought I’d use /usr/share/bob because it has no @
> > but that doesn’t work either:
>
> > + svn cohttp://code.djangoproject.com/svn/django/trunk/django-trunk
> > svn: Working copy 'django-trunk' locked
> > svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for
> > details)
> > r...@pubuntu:/usr/share/bob# svn cleanup
> > svn: '.' is not a working copy directory
>
> The working copy here is /usr/share/bob/django-trunk, not /usr/share/bob, so
> that is where you'll need to run svn cleanup from in order to fix whatever
> has gotten messed up as far as svn is concerned. But it wasn't necessary to
> put a copy of Django here in the first place so you may just want to delete
> this tree and use the one you put in your own home tree somewhere.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
