In my system there is Django 1.2.3 installed system wide:
C:\\>python -c \"import django; print django.get_version()\"
1.2.3
C:\\>django-admin.py --version
This is because your windows has associated .py
extension with the globally installed python.exe
. Therefore when you type django-admin.py
, even though you're in a virtualenv, the global python is invoked, and it in turn finds your global django installation in its own site-packages. Try python django-admin.py
to circumvent the association.