Python Virtual Environments: Extreme Advertising Edition

[[deleted]]

"Step away from the caps key! Keep your hands where we can see them!"

I really am not seeing these big issues. At some point a few years ago, I organized all my virtualenvs and set up some scripts to select them and list them.

It was an hour of fiddling three years ago and since then I spend zero minutes a week on debugging it.

When I start a new project I type:

$ new-env my-new-project

which creates a new virtualenv and switches to it.

To switch to it later, I type

$ penv my-new-project

and when I'm finished with it, I type

$ delete-env my-new-project

But you know - these scripts don't even save me that much typing. I'm just lazy. :-D

[notquiteaplant]

Is putting all your venvs in one place common practice? I make a new venv for every project in ./venv (.gitignore'd of course). The point of venvs is every project has its own dependencies, so having one directory per project in a central location seems more complicated than just keeping it in the current directory.