Re: tutorial first step. -ImportError: No module named django.core-

I am sure I activated the environment but nothing. In my case I guess I had some problem with the PATH variable.. 2012/11/9 Dan Gentry > Quick note: when using virutalenv on Windows, one runs the activate script > to use the environment. \Scripts\activate.bat > > Same

Re: tutorial first step. -ImportError: No module named django.core-

Quick note: when using virutalenv on Windows, one runs the activate script to use the environment. \Scripts\activate.bat Same function as the source command in Linux. Dan Gentry >> -- You received this message because you are subscribed to the Google Groups "Django users" group. To view

Re: tutorial first step. -ImportError: No module named django.core-

Francesco and Elena, I read up on virtualenv and to my understanding, what you said was right - that it sets the PATH for you just by using it. One thing that I'm still not sure on, is that for Linux, you have to specify the 'source' command which will change the environment in place. I'm

Re: tutorial first step. -ImportError: No module named django.core-

Elena, I think the place where should be put a warning about which django-admin.py script has to be run is here. Hence when the reader is going to install virtualenv. Hoping this help Franz 2012/11/8 Elena

Re: tutorial first step. -ImportError: No module named django.core-

Francesco and Daniel, This is an interesting problem with the tutorial! We will have to make sure that it's changed -- obviously the tutorial needs to be clearer! Any suggestions you guys have about how/where we could insert some information that could make this clearer *please* point out where

Re: tutorial first step. -ImportError: No module named django.core-

Good good! So, this means I was executing the wrong django-admin.py file. Daniel, I'm curious about your question, too. Because I though that activating virtualenv the path is automatically set to the specified environment and then no need to include the right django-admin.py file into some

Re: tutorial first step. -ImportError: No module named django.core-

Hi Elena, I actually had the exact same problem Francesco was having. I wasn't able to start a project, and then I tried your question. The cmd line went something like this: (env) path/to/directory/python env/Scripts/django-admin.py startproject newproject It worked! While I'm happy with

Re: tutorial first step. -ImportError: No module named django.core-

Hi Elena, Thanks for your replies. Sorry, but in the end I started a new installation without virtualenv because I was curious about django and I didn't want to wait. When I will use again virtualenv (I know I'll do) I'll try again to do my best. Thanks for you help, really! Francesco

Re: tutorial first step. -ImportError: No module named django.core-

Hi Francesco, What happens when you try: $ cd C:\Python27\fra_env\ (or whatever the equivalent of this might be in the shell you are using) $ python Scripts\django-admin.py startproject mysite Regards, Elena :) On Mon, Nov 5, 2012 at 1:19 AM, Francescos wrote:

Re: tutorial first step. -ImportError: No module named django.core-

Hi Elena, Thanks for replying. I guess the PATH var is well set. In fact, if I hit python into cmd.exe and then import django everything work (I can print the django version, as well). So, Django is installed and reachable apparently. At this point I guess there is a problem in looking for the

Re: tutorial first step. -ImportError: No module named django.core-

Hi Francesco, What you're seeing is the most basic django/python error. It means that your python can't find django from your current path. You should start by checking for the simple things. What happens when you try putting the following in your terminal?: $ python and then: >>> import

tutorial first step. -ImportError: No module named django.core-

Hello everyone, Following the django tut I've sat up all the installation and reached the step where I had to run the command: django-admin.py startproject mysite result: I receive the error specified in the subject. I installed virtualenv (as said