Re: ImportError: No module named django.core

activate your virtualenv. Mrinmoy Das http://goromlagche.in/ On Mon, Jan 13, 2014 at 5:47 PM, wrote: > I get this error while creating New Project. > > radhika$ django-admin.py startproject housing > > Traceback (most recent call last): > > File "/usr/local/bin/django-admin.py", line 2, in

Re: ImportError No module named django.core

Hi, I am as noob as you so maybe this is a case of blind leading blind. From what I hear it is considered best practice to first create a virtualenv and then install django and any other packages inside that virtualenv. Read here for virtualenv http://dabapps.com/blog/introduction-to-pip-and-vi

Re: ImportError: No module named django.core

Hi Nuno, Thanks for helping, but it turned out it has nothing to do with the PYTHONPATH but with access rights of the /usr/local and /usr/local/lib (http://blog.petrovic.gr/lang/en-us/2010/05/importerror-no-module- named-django-core/) Thanks, On May 31, 11:55 am, Nuno Maltez wrote: > Well, it

Re: ImportError: No module named django.core

Well, it seems that your python lib is at /usr/lib/python2.6/dist-packages: > mx:~/webapps$ python -c "from distutils.sysconfig import > get_python_lib; print get_python_lib()" > > /usr/lib/python2.6/dist-packages but django is in "local" - /usr/local/lib/python2.6/dist-packages > /usr/local/lib