python django: create a new virtualenv for each django project?
Personally I do.
Virtualenvs help you keep the dependencies required for a project organised and manageable. If you have a django 1.7 project, it will require django1.7 and thus install it in your virtualenv. Without a virtualenv, you might decide to take on a project that requires django1.10. This means your django1.7 project might break. To avoid such a scenario use a virtual environment.
Do you create a new virtualenv every time you start a new project?
I'm going through some tutorials on the web and they create a virtualenv first then pip install django in the virtualenv. But there's one tutorial that i saw saying that you wouldn't create a project within the virtualenv and its only used for dependencies.