django import error – No module named

django import error – No module named

Ok, I see plenty of these errors around. I have tried everything I know to do and have yet to figure this out.
I am working on a development server running python 2.5 and Django 1.3. Django 1.3 was installed using python install after unpacking the tar.gz download.
All works well, I seldom have the need to run but am trying to use the new staticfiles app and am running into problems.
python collectstatic
Traceback (most recent call last):
  File "", line 2, in 
    from import execute_manager
ImportError: No module named

Ok, so I have PATH issue.
From Django install I double check my site-packages directory.
python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()"

Ok, let's check out what I have, echo $PYTHON_PATH was empty, so I set it
export PYTHON_PATH=/usr/lib/python2.5/site-packages/django

Still no luck. Lets check what sys.path has to say
>>> import sys
>>> print sys.path
['', '/usr/lib/python2.5', '/usr/lib/python2.5/plat-linux2', '/usr/lib/python2.5/lib-tk', '/usr/lib/python2.5/lib-dynload', '/usr/local/lib/python2.5/site-packages', '/usr/lib/python2.5/site-packages', '/usr/lib/python2.5/site-packages/PIL', '/usr/lib/python2.5/site-packages/django', '/var/lib/python-support/python2.5']

path is there, I even created /usr/lib/python2.5/site-packages/django.pth with contents
cat /usr/lib/python2.5/site-packages/django.pth 

Anyone got an clues to what is going on here? 
I found a symlink further up the path that was getting in the way, but no on to a new error.
python collectstatic
Traceback (most recent call last):
  File "", line 14, in 
  File "/usr/lib/python2.5/site-packages/django/core/management/", line 438, in execute_manager
  File "/usr/lib/python2.5/site-packages/django/core/management/", line 349, in execute
  File "/usr/lib/python2.5/site-packages/django/", line 12, in get_version
    from django.utils.version import get_svn_revision
ImportError: No module named utils.version

I also tried creating a new project to see if there were any issues there and get the same utils.version error.
Side node: Unode from #django helped me a bit, set up virtualenv on same machine and got past the errors so still not sure what is up with this actual install here, but it seems to not be in the django projects but in the django/python install.


Answer 1:

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).

Answer 2:

If you are in a virtualenv you need to activate it before you can run ./ ‘command’

source path/to/your/virtualenv/bin/activate

if you config workon in .bash_profile or .bashrc

workon yourvirtualenvname

*please dont edit your file maybe works by isnt the correct way and could give you future errors

Answer 3:

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:

$ source ./bin/activate
$ pip install Django

Answer 4:

Please, reinstall django with pip:

sudo pip install --upgrade django==1.3

(Replace 1.3 to your django version)

Answer 5:

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 6:

Another possible reason for this problem is that your OS runs python3 by default.

Either you have to explicitly do: python2

or you need to edit the shebang of, like so:

#!/usr/bin/env python2

or if you are using python3:

#!/usr/bin/env python3

Answer 7:

I had this error while trying to run an embedded system (using django of course) on a Raspberry Pi 2 (and not a VM)

Running this:

 sudo pip install Django

Made the trick!

  • just in case a fellow using Raspbian/Jessie gets this

Answer 8:

You are probably using virtualenvwrapper. Don’t forget to select your enviroment by running:

$ workon env_name

Answer 9:

For me, my server was using Python 2.4. I simply looked up Python 2.7, which was installed on my server, and created an alias.

alias python=python2.7

If you need to know more, I found the solution here

Answer 10:

I was getting the same problem while I trying to create a new app. If you write python startapp myapp, then it looks for usr/bin/python. But you need this “python” which is located in /bin directory of your virtual env path. I solved this by mentioning the virtualenv’s python path just like this:

<env path>/bin/python startapp myapp

Answer 11:

Try change your first line of




#!/usr/bin/env python

Answer 12:

python3 runserver

Check version of Python

Answer 13:

Solved it!!!

After searching for ages and trying all these other suggestions which didn’t work, I finally found the solution for my setup.

My setup/scenario:

  • Windows, Python27
  • My django project is checked out via svn
  • when running python runserver in the new folder, I got the import error
  • python runserver used to work in the original folder (which I would commit changes from) until I deleted it


Remove any the folder named django in the same directory of

Thats right…as soon as I removed the folder “django” which only contained a file…I could run the server again!

Have no idea why though

Answer 14:

For those of you using Django 1.6 or newer, note that execute_manager was removed. There is a solution posted in the second SO answer here.