On May 12, 10:43 am, Alice Zoë Bevan–McGregor <[email protected]> wrote: > > How do you name virtual environments? > > And where do you store this enviroments? > > Exists any recipe to manage several virtual envs and not die trying > > it? :) > > I have a Projects folder in my home folder. Inside this folder I have > one folder per major project. E.g. > > ~/Projects/inLocation > ~/Projects/Rogue > ~/Projects/GothCandy > ~/Projects/Experiments
I use a similar structure, perhaps giving the virtualenv the same name as the Python package I'm working on in that venv. Really, the name doesn't matter except that it's descriptive (if you have multiple unrelated envs named trunk for example, that could be confusing). On my dev machine, I'll usually just have one venv per project (for trunk). On a server, I might have multiple tagged venvs for a project, like ~/Projects/MyProject-rel-0.1. You might be interested in virtualenvwrapper: http://www.doughellmann.com/projects/virtualenvwrapper/. It lets you do things like `$ workon MyProj` instead of `$ cd MyProj; source bin/ activate`. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
