I\'ve recently installed Django-1.5b1. My system configuration:
When I call django-
I've had the same issue as you, and I haven't come up with a good fix aside from prepending my project folder to the PYTHONPATH like this:
export PYTHONPATH="/absolute/path/to/django/project/folder:$PYTHONPATH"
where my
is located at /absolute/path/to/django/project/folder/
. I add that export
command to the end of my env/bin/activate
script so it happens every time I initialize the virtualenv.
The only difference between our two situations is that I use multiple settings files instead of a single settings.py
module.
You can also call django-admin.py
from the folder containing your Django project like so:
python ~/.virtualenvs/devel/bin/django-admin.py
so that it recognizes your current working directory as part of the path.
Hope that makes sense. It's kind of clumsy to explain which makes it hard to search for an answer.