django import error - No module named core.management

Question

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 setup.py install after unpacking the tar.gz download.

All works well, I seldom have the need to run manage.py but am trying to use the new staticfiles app and am running into problems.

python manage.py collectstatic
Traceback (most recent call last):
  File "manage.py", line 2, in <module>
    from django.core.management import execute_manager
ImportError: No module named core.management

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()"
/usr/lib/python2.5/site-packages

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 
/usr/lib/python2.5/site-packages/django/

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 manage.py collectstatic
Traceback (most recent call last):
  File "manage.py", line 14, in <module>
    execute_manager(settings)
  File "/usr/lib/python2.5/site-packages/django/core/management/__init__.py", line 438, in execute_manager
    utility.execute()
  File "/usr/lib/python2.5/site-packages/django/core/management/__init__.py", line 349, in execute
    version=get_version(),
  File "/usr/lib/python2.5/site-packages/django/__init__.py", 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.

What happens when you type `import django` into the python shell? — silent1mezzo, May 18 '11 at 19:26
@silent1mezzo - Ahh forgot to throw that in, no complaints from the python shell on import django — grantk, May 18 '11 at 19:27
@silentmezzo - Not on this machine, did so on my personal machine before moving the project. — grantk, May 18 '11 at 19:44
@silent1mezzo same issue there, as well as creating a new project. — grantk, May 18 '11 at 19:48
This looks like an installation problem. I can't pinpoint what the problem is but using a virtualenv to hold your Django install will probably fix the problem. Can you try that? Just get `virtualenv`, do a `virtualenv --no-site-packages ~/env`. Then do a . ~/env/bin/activate and then a `pip install django==1.3`. Try your regular commands after that and see if they work. — Noufal Ibrahim, May 18 '11 at 20:33
Closing as this does not seem to be an issue with Django or the projects but the server itself. -- and nevermind, I was hoping I could close it myself, but just have the normal close options. — grantk, May 18 '11 at 21:00

Steve K · Answer 1 · 2014-06-03T15:24:07.157

175

If, like me, you are running your django in a virtualenv, and getting this error, look at your manage.py. 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).

edited Jun 03 '14 at 15:24

answered May 25 '12 at 14:42

Steve K

10,879
4
39
39

31

or run like `/bin/python manage.py runserver` – geekQ Jun 10 '12 at 08:43
Well spotted! That exactly was the problem! – stratis Aug 18 '12 at 20:19
7

Also, er... remember to activate the virtualenv. D'oh! – Alex Mcp Dec 16 '13 at 20:47
1

Anyway you could provide an example of the path to your python executable in your virtualenv. For example my path to my virtual env is /Users/Chris/virtualenv/my_first_venv and I made the first line #!/Users/Chris/virtualenv/my_first_venv/, but I still get the same error. I think I may be doing something wrong with the shebang... – Chris Jun 03 '14 at 05:27
You might have forgotten to add the python executable at the end of the path : `#!/Users/Chris/virtualenv/my_first_venv/bin/python` or something along this ? – Steve K Jun 03 '14 at 12:20
32 down vote If you are in a virtualenv you need to activate it before you can run ./manage.py 'command' source path/to/your/virtualenv/bin/activate if you config workon in .bash_profile or .bashrc use workon yourvirtualenvname *please dont edit your manage.py* file maybe works by isnt the correct way and could give you future errors – elin3t Jul 21 '16 at 13:14
how do we find the environment? – SumNeuron Sep 13 '17 at 11:49
Interesting scenario: only raises `ImportError` when I run `sudo python ...`. This is because sudo and user use different pythons! Run `sudo /path/to/users/python ...` instead. – polarise Mar 03 '18 at 20:45

score 42 · Answer 2 · answered Jun 11 '13 at 18:07

42

If you are in a virtualenv you need to activate it before you can run ./manage.py 'command'

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

if you config workon in .bash_profile or .bashrc

workon yourvirtualenvname

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

answered Jun 11 '13 at 18:07

elin3t

1,881
1
24
29

This did it for me too after burning half of the night struggling to make it work. Thank you a whole lot @elin3t. – Yax Jul 16 '14 at 00:29

score 31 · Answer 3 · answered Dec 27 '13 at 14:19

31

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

answered Dec 27 '13 at 14:19

aviggiano

1,204
17
23

But without sudo you get: OSError: [Errno 13] Permission denied: '/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/django' – malhal Oct 17 '16 at 22:33
@aviggiano Thank you!!! I was struggling for likt 30 mins trying to figure this out...I'm a Noob to Django, So thank you for this! – Aaron Cloud May 30 '21 at 04:34

score 19 · Answer 4 · answered May 18 '11 at 19:29

19

Please, reinstall django with pip:

sudo pip install --upgrade django==1.3

(Replace 1.3 to your django version)

answered May 18 '11 at 19:29

satels

789
6
13

27

Not recommended. Using `sudo` to install into the system directories will interfere with native packages and most probably break atleast some parts of your python install. I'd recommend virtualenv. – Noufal Ibrahim May 18 '11 at 20:34

score 13 · Accepted Answer · answered May 19 '11 at 14:08

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.

score 9 · Answer 6 · edited Nov 06 '19 at 06:52

9

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

Either you have to explicitly do: python2 manage.py

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

#!/usr/bin/env python2

or if you are using python3:

#!/usr/bin/env python3

edited Nov 06 '19 at 06:52

Sebastian Kaczmarek

8,120
4
20
38

answered Sep 20 '12 at 12:04

nuts

715
8
22

for me, I had to do `#!/usr/bin/env python2.7` – Vic Jan 02 '18 at 18:45

score 7 · Answer 7 · edited Jul 10 '15 at 12:04

7

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

$ workon env_name

edited Jul 10 '15 at 12:04

pedrostanaka

711
1
9
16

answered Mar 31 '15 at 10:02

M K

9,138
7
43
44

d1jhoni1b · Answer 8 · 2016-08-11T21:55:27.740

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

edited Aug 11 '16 at 21:55

answered Jun 02 '16 at 01:56

d1jhoni1b

7,497
1
51
37

score 5 · Answer 9 · edited Jul 31 '17 at 14:26

5

python3 manage.py runserver

Check version of Python

edited Jul 31 '17 at 14:26

Bugs

4,491
9
32
41

answered Jul 30 '17 at 10:56

score 4 · Answer 10 · answered Aug 11 '12 at 22:45

4

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

answered Aug 11 '12 at 22:45

el_stack

538
3
12

Tarique · Answer 11 · 2014-01-22T18:56:02.753

4

I was getting the same problem while I trying to create a new app. If you write python manage.py 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 manage.py startapp myapp

edited Jan 22 '14 at 18:56

answered Jan 22 '14 at 18:48

Tarique

4,017
1
26
25

score 4 · Answer 12 · edited Mar 28 '18 at 13:14

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 manage.py runserver in the new folder, I got the import error
python manage.py runserver used to work in the original folder (which I would commit changes from) until I deleted it

Solution

Remove any the folder named django in the same directory of manage.py

Thats right...as soon as I removed the folder "django" which only contained a __init__.py file...I could run the server again!

Have no idea why though

Because a folder with a \_\_init\_\_.py file is treated as a **python** module. So you should not name the implied module directory __django__ — kaushal agrawal, Mar 28 '18 at 12:38

score 3 · Answer 13 · answered Jan 17 '13 at 13:51

3

Try change your first line of manage.py.

Change

#!/usr/bin/python

by

#!/usr/bin/env python

answered Jan 17 '13 at 13:51

Gabriel Cavalcante

111
4

3

The reverse helped me. Replaced `#!/usr/bin/env python` by `#!/usr/bin/python` – curlyreggie Nov 21 '13 at 12:59
env is a common unix bin to get os environment bin links, depending on OS configuration or python installation the bin may reside in a different path than /usr/bin/ and your solution will not work, also will not work if 'env' bin is installed in a different location. – Gabriel Cavalcante Feb 08 '14 at 14:31

score 2 · Answer 14 · edited May 23 '17 at 12:02

2

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.

edited May 23 '17 at 12:02

Community

1
1

answered Jan 17 '14 at 20:25

Owen

3,063
5
30
26

score 2 · Answer 15 · answered Jul 13 '15 at 05:51

2

Store the python python path in a variable and execute.This would include the otherwise missing packages.

python_path= `which python` 
$python_path manage.py runserver

answered Jul 13 '15 at 05:51

Nischay Gulati

243
3
12

score 2 · Answer 16 · edited Dec 16 '19 at 13:59

==================================SOLUTION=========================================

First goto: virtualenv

by running the command: source bin/activate

and install django because you are getting the error related to 'import django':

pip install django

Then run:

python manage.py runserver

(Note: please change 'runserver' to the program name you want to run)

For the same issue, it worked in my case. ==================================Synopsis=========================================

ERROR:
(Development) Rakeshs-MacBook-Pro:src rakesh$ python manage.py runserver
Traceback (most recent call last):
  File "manage.py", line 8, in <module>
    from django.core.management import execute_from_command_line
ModuleNotFoundError: No module named 'django'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "manage.py", line 14, in <module>
    import django
ModuleNotFoundError: No module named 'django'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "manage.py", line 17, in <module>
    "Couldn't import Django. Are you sure it's installed and "
ImportError: Couldn't import Django. Are you sure it's installed and available on your PYTHONPATH environment variable? Did you forget to activate a virtual environment?
(Development) Rakeshs-MacBook-Pro:src rakesh$ 
(Development) Rakeshs-MacBook-Pro:src rakesh$ 
(Development) Rakeshs-MacBook-Pro:src rakesh$ python -Wall manage.py test
Traceback (most recent call last):
  File "manage.py", line 8, in <module>
    from django.core.management import execute_from_command_line
ModuleNotFoundError: No module named 'django'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "manage.py", line 14, in <module>
    import django
ModuleNotFoundError: No module named 'django'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "manage.py", line 17, in <module>
    "Couldn't import Django. Are you sure it's installed and "
ImportError: Couldn't import Django. Are you sure it's installed and available on your PYTHONPATH environment variable? Did you forget to activate a virtual environment?

AFTER INSTALLATION of django:

(Development) MacBook-Pro:src rakesh$ pip install django
Collecting django
  Downloading https://files.pythonhosted.org/packages/51/1a/e0ac7886c7123a03814178d7517dc822af0fe51a72e1a6bff26153103322/Django-2.1-py3-none-any.whl (7.3MB)
    100% |████████████████████████████████| 7.3MB 1.1MB/s 
Collecting pytz (from django)
  Downloading https://files.pythonhosted.org/packages/30/4e/27c34b62430286c6d59177a0842ed90dc789ce5d1ed740887653b898779a/pytz-2018.5-py2.py3-none-any.whl (510kB)
    100% |████████████████████████████████| 512kB 4.7MB/s 
Installing collected packages: pytz, django

AFTER RESOLVING:

(Development) MacBook-Pro:src rakesh$ python manage.py runserver
Performing system checks...

System check identified no issues (0 silenced).

You have 15 unapplied migration(s). Your project may not work properly until you apply the migrations for app(s): admin, auth, contenttypes, sessions.
Run 'python manage.py migrate' to apply them.

August 05, 2018 - 04:39:02
Django version 2.1, using settings 'trydjango.settings'
Starting development server at http://127.0.0.1:8000/
Quit the server with CONTROL-C.
[05/Aug/2018 04:39:15] "GET / HTTP/1.1" 200 16348
[05/Aug/2018 04:39:15] "GET /static/admin/css/fonts.css HTTP/1.1" 200 423
[05/Aug/2018 04:39:15] "GET /static/admin/fonts/Roboto-Bold-webfont.woff HTTP/1.1" 200 82564
[05/Aug/2018 04:39:15] "GET /static/admin/fonts/Roboto-Light-webfont.woff HTTP/1.1" 200 81348
[05/Aug/2018 04:39:15] "GET /static/admin/fonts/Roboto-Regular-webfont.woff HTTP/1.1" 200 80304
Not Found: /favicon.ico
[05/Aug/2018 04:39:16] "GET /favicon.ico HTTP/1.1" 404 1976

Good luck!!

score 2 · Answer 17 · edited Aug 15 '21 at 10:39

2

environment: Python 3.9.6, Django 3.2.6, VS Code

Just disable Pylance extension and reload your VS Code.

edited Aug 15 '21 at 10:39

lejlun

4,140
2
15
31

answered Aug 12 '21 at 00:23

Michael Zhang

21
1

score 1 · Answer 18 · answered May 14 '14 at 07:40

This error usually occurs when django is not installed. If you have already installed django but still getting the same error, then you must be working in separate virtual environment. You need to install django in your virtual environmnent as well. When you are in shell of virtual machine simply do this:

pip install django

It is because virtual machine has separate file system, it doesn't recognize django even if it is installed on your system.

score 1 · Answer 19 · answered Jul 30 '14 at 17:59

1

I fixed this problem by changing #PATH="$VIRTUAL_ENV/bin:$PATH" to PATH="$PATH:$VIRTUAL_ENV/bin" For reasons not obvious to me the python executable in the virtualenv dir does not see django but the normally installed python does.

answered Jul 30 '14 at 17:59

Lowlysquib

11
1

score 1 · Answer 20 · answered Jun 07 '21 at 10:57

1

Just a single mistake This happened with me as well. My mistake was that I've created Django project before creating virtual env, later activated the env and was trying to start the server. Just install Django after activating env it will work

answered Jun 07 '21 at 10:57

Ayaan Kaifullah

75
1
4

score 1 · Answer 21 · answered Jan 17 '12 at 22:45

1

I had a similar problem. PyCharm couldn't run the server but I could run it from the command line. I tried which python and then made sure that PyCharm was same interpreter and then everything worked OK.

answered Jan 17 '12 at 22:45

Trip Denton

11
1

score 0 · Answer 22 · answered Apr 03 '13 at 14:00

Agreed completely that this is a path issue but fwiw, I had this same error. It was due to the mistake of using a relative path for my Python executable when setting up my virtual environment. I had done this:

virtualenv -p ~/python_runtimes/2.7.3/bin/python venv2.7.3 --distribute

Instead I had to give the full path to the Python executable.

HTH, Harlin

score 0 · Answer 23 · answered Apr 22 '13 at 02:12

0

source ~/blog-venv/bin/activate

pick your virtualenv to replace "blog-venv" here.

answered Apr 22 '13 at 02:12

windmaomao

7,120
2
32
36

Thanks, that solved my problem with respect to this: `File "manage.py", line 8, in from django.core.management import execute_from_ ImportError: No module named django.core.management` – Shailen Jun 03 '13 at 14:39

score 0 · Answer 24 · answered Oct 10 '13 at 17:00

Be sure you're running the right instance of Python with the right directories on the path. In my case, this error resulted from running the python executable by accident - I had actually installed Django under the python2.7 framework & libraries. The same could happen as a result of virtualenv as well.

score 0 · Answer 25 · answered May 03 '14 at 10:22

Okay so it goes like this:

You have created a virtual environment and django module belongs to that environment only.Since virtualenv isolates itself from everything else,hence you are seeing this.

go through this for further assistance:

http://www.swegler.com/becky/blog/2011/08/27/python-django-mysql-on-windows-7-part-i-getting-started/

1.You can switch to the directory where your virtual environment is stored and then run the django module.

2.Alternatively you can install django globally to your python->site-packages by either running pip or easy_install

Command using pip: pip install django

then do this:

import django print (django.get_version()) (depending on which version of python you use.This for python 3+ series)

and then you can run this: python manage.py runserver and check on your web browser by typing :localhost:8000 and you should see django powered page.

Hope this helps.

score 0 · Answer 26 · answered Dec 09 '15 at 19:23

0

I included the name of the new App to the INSTALLED_APPS list in the settings.py "before" I issued the startapp command. Once I removed the list entry, I could create the app.

answered Dec 09 '15 at 19:23

Milad M

1,538
2
13
13

score 0 · Answer 27 · answered Dec 23 '16 at 09:52

0

I solved this problem by using 'django-admin' command as following instead:

django-admin startproject _project_name

just remove the ".py" attached to "django-admin"

answered Dec 23 '16 at 09:52

Haziq

2,048
1
16
27

score 0 · Answer 28 · answered Jul 11 '18 at 16:04

0

Having an application called site can reproduce this issue either.

answered Jul 11 '18 at 16:04

Christian Gutierrez Sierra

87
6

score 0 · Answer 29 · answered Jul 14 '19 at 20:27

0

I got this due to forgetting that I installed Django using pip -U, so it was only available to the user running my Django app. To run manage.py I had to do

sudo su -s /bin/bash MY_DJANGO_USER
/PATH/TO/MY/APP/manage.py

answered Jul 14 '19 at 20:27

EM0

5,369
7
51
85

score 0 · Answer 30 · answered May 18 '11 at 19:37

0

your project is created using an old version of django-admin.py, older than django1.3

to fix this create another django project and copy its manage.py and paste it in the old one

answered May 18 '11 at 19:37

MBarsi

2,417
1
18
18

@dontario. Not this one, I created this project using my personal computer running 1.3.0 final. There are some imported projects that were created with an older version could that be it? – grantk May 18 '11 at 19:40
I tried copying my new mange.py from the new application to the old application that is used as well and still get the same error. – grantk May 18 '11 at 19:42

score 0 · Answer 31 · edited Dec 24 '21 at 20:33

0

That's an interpreter error.

If you are using vscode then just follow these steps:

View
Command palette
Search for python
Select interpreter
Select windows store and your problem will get solved, after few seconds the errors have gone.

This problem occurs due to path changed.

edited Dec 24 '21 at 20:33

Paul

1,801
1
12
18

answered Dec 23 '21 at 13:12

kanishk yadav

1
1

score -2 · Answer 32 · answered Jan 27 '16 at 19:27

-2

all of you guys didn't mention a case where someone "like me" would install django befor installing virtualenv...so for all the people of my kind ther if you did that...reinstall django after activating the virtualenv..i hope this helps

answered Jan 27 '16 at 19:27

oajmi

187
1
1
14

This isn't a solution. It's a comment on another solution by Steve k. – shanemgrey May 23 '16 at 14:05
that's what happened to me and that's how i fixed it...it's a mistake any beginner could fall into – oajmi Jan 08 '17 at 19:50

django import error - No module named core.management

32 Answers32

AFTER INSTALLATION of django:

AFTER RESOLVING:

Linked