Hello, The error you're seeing is due to Django not being installed in your virtual environment.
virtualenv is the way to go, unless you have an incredibly good reason not to use it. It couldn't possibly break anything as it installs virtual environments alongside your system wide Python. If you used the --no-site-packages option, you will need to install everything for that virtual environment as it won't have copied the libraries that were already in your system. This is a good thing. It will give you a clean slate to start from. Proceed to install everything through pip while *in* the newly created environment. Remember pip can install from most VCS repositories, so consult the docs should you need to do that.. The main advantage of using virtualenv is that you can keep things separate. Imagine you want to work on two different Django projects, and one of them is a maintenance job for something that was coded back when 1.0 was released, while the other is an upcoming website built on the dev branch. If you install just one instance of Django for the whole system you won't be able to work on both. For more info, google "notes on using pip and virtualenv". It should have everything you need. I'm sorry for not linking anything but I'm typing on my phone while my pupils finish dilating before an eye exam, so this is hard enough without multitasking! ;-) Also google virtualenvwrapper and *read through the docs* including the user submitted tips! Good luck and happy coding! Cheers, AT On Jan 5, 2012 5:02 PM, "Alec Taylor" <alec.tayl...@gmail.com> wrote: > > Good morning, > > On my system (Windows 8 Developer Preview x64 with Python 2.7.2 x64) I > painstakingly installed all the dependencies for Django, Satchmo and a > few other large scale projects. > > (about 10% couldn't be installed with pip, which is why I use the word > 'painstakingly') > > Recently though I needed Pinax for something, so following there guide > (http://pinax.readthedocs.org/en/latest/gettingstarted.html) I setup a > virtualenv for it. > > Not only could I not get Pinax running, but when I went back to work > on my Satchmo-based project, and ran "manage.py runserver" I got the > following error: > Traceback (most recent call last): > File "P:\Prototype\Django\store\manage.py", line 18, in <module> > from django.core.management import execute_manager > ImportError: No module named django.core.management > > Typing in `import django` from the interpreter gives me: > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > ImportError: No module named django > > Does this mean I need to install everything required by my project all > over again? - If so, should I take a virtualenv approach (and what > would the advantages be of doing so)? > > Thanks for all suggestions, > > Alec Taylor > > -- > You received this message because you are subscribed to the Google Groups "Django users" group. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
