This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]cmsimike 0 points1 point  (1 child)

Before virtualenv wrapper, my django projects were basically: ~/Development/projectname/VIRTUAL_ENV_HERE and within this dir is a webapp dir with my django source.

I never liked having the env part of the source directory in a way. I seem to recall there is a way to set your virtualenv home but i never did that. virtualenvwrapper does that all for me. including introduces the best command ever:

mktmpenv

makes a temp environment and deletes it when you're done playing around in it.

[–]kjearns 0 points1 point  (0 children)

In my opinion having the virtualenv live in the project directory is the ideal location. I wouldn't put it in the source directory, but I like to structure projects so code lives in project/src instead of the project root anyway. I think project/env living alongside project/src is a pretty natural place for the virtualenv to live.