Python + Django + Virtualenv importing django.core failed

Question

I'm using Python 2.7.3 on Windows 7. I've set PATH as a C:\python27 which is a original python binary path.

First, I made a new Virtualenv named "django" without any options,

virtualenv django

Second, activated Virtualenv,

c:\workspace\py-envs\django\Scripts\activate

Third, installed Django by using pip,

pip install django

Fourth, just executed django-admin.py startproject SOME_NAME like below.

Then, I faced an issue while importing django.core package.

FAILED

(django) c:\workspace\python>django-admin.py startproject a
(django) c:\workspace\python>python django-admin.py startproject a
(django) c:\workspace\python>c:\py-envs\django\Scripts\python django-admin.py startproject a

ERROR message

Traceback (most recent call last):
  File "C:\workspace\py-envs\django\Scripts\django-admin.py", line 2, in <module>
    from django.core import management
ImportError: No module named django.core

WORKED

(django) c:\workspace\python>python c:\py-envs\django\Scripts\django-admin.py startproject a

CHECKED

django-admin.py exists in c:\py-envs\django\Scripts\
virtualenv added C:\py-envs\django\Scripts\ line in PATH (checked with echo %PATH%)
pip freeze result only shows Django==1.5

I'd like to start a project by using the first command:

python django-admin.py startproject a

What else I can do?

possible duplicate of django-admin.py and virtualenv issue on Windows — Lie Ryan
– Lie Ryan, Commented Feb 27, 2013 at 9:45
@LieRyan Unfortunately, I haven't installed Django on normal environment. I only installed on my virtual env. I also checked that normal env didn't have django-admin.py file in \Scripts folder and virtualenv shows proper version number. — Namwoo Kim
– Namwoo Kim, Commented Feb 27, 2013 at 23:58

Stéphane Bruckert · Accepted Answer · 2014-11-20 21:02:58Z

2

Under a virtual environment (virtualenv), the only default way to call django-admin is to call it by django-admin.py.

The following works:

django-admin.py startproject PROJECT_NAME,

The following doesn't:

django-admin startproject PROJECT_NAME,
python django-admin startproject PROJECT_NAME,
python django-admin.py startproject PROJECT_NAME.

answered Nov 20, 2014 at 21:02

Stéphane Bruckert

23.1k15 gold badges102 silver badges136 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Mateus Padua · Accepted Answer · 2014-02-18 13:00:49Z

1

This happen because the windows python interpreter use the global interpreter always and not the current python virtualenv interpreter.

Example:
C:\python27\python.exe # windows always use it

and not this

C:\envs\my_env\Scripts\python.exe

In oficial documentation, I found this: http://docs.python.org/2/using/cmdline.html?highlight=#-m
"When called with -m module-name, the given module is located on the Python module path and executed as a script."

if you type in console, echo %PATH%, will see the virtualenv path in first. Therefore

(django) c:\workspace\python>python -m django-admin startproject my_new_project

should work

edited Feb 18, 2014 at 13:00

answered Feb 18, 2014 at 12:53

Mateus Padua

1932 silver badges8 bronze badges

Collectives™ on Stack Overflow

Python + Django + Virtualenv importing django.core failed

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related