As known this was a path issue.
the base of my custom packages shared a name with a directory set in a /etc/profile. The packages were in a different location however for the webserver. So I removed the offending entries from my $PYTHONPATH and was good to go!
Thanks for the help.Answer #2 98.8 %
If, like me, you are running your django in a virtualenv, and getting this error, look at your
The first line should define the python executable used to run the script.
This should be the path to your virtualenv's python, but it is something wrong like /usr/bin/python, which is not the same path and will use the global python environment (and packages will be missing).
Just change the path into the path to the python executable in your virtualenv.
You can also replace your shebang line with
#!/usr/bin/env python. This should use the proper python environment and interpreter provided that you activate your virtualenv first (I assume you know how to do this).
If you are in a virtualenv you need to activate it before you can run ./manage.py 'command'
if you config workon in .bash_profile or .bashrc
*please dont edit your manage.py file maybe works by isnt the correct way and could give you future errorsAnswer #4 100 %
I had the same problem because I was installing Django as a super user, thus not in my virtualenv. You should not do
sudo pip install Django
Instead, install it this way:
Answer #5 80 %
$ source ./bin/activate $ pip install Django
Please, reinstall django with pip:
sudo pip install --upgrade django==1.3
(Replace 1.3 to your django version)