3 ms·

It's funny how people seem to love this node style of a virtualenv in the project. I much, much prefer virtualenvwrapper with it's style of keeping the environ

by stuaxo 3y ago

It's funny how people seem to love this node style of a virtualenv in the project. I much, much prefer virtualenvwrapper with it's style of keeping the environment outside the project. This way, I don't end up with lots of huge directories hidden in the many many projects I check out. The other thing that can't happen is accidentally adding the folder to version control. I can have various versions of my project checkout out, and use the same venv between them. I can quickly fire up a venv for the project with a different version of python. I can quickly list all my venvs, and prune them as needed. While people may say "we have infinite storage" my laptop only has 2tb and I fill it up. But each to their own, a lot of people seem to like it. I also use direnv, and the the virtualenvwrapper plugin for zsh, and have defaults - in this case it automatically defaults to the virtualenv with the same name as the directory I enter, but I didn't have to do any config for that to happen.

globular-toast 3y ago
> The other thing that can't happen is accidentally adding the folder to version control. A few other ways I've seen embedded venvs interfering, off the top of my head: * Polluting output from tools like `find`, `grep` and `tree` (yes, some have .gitignore options, but you have to remember to use them and some don't have the option at all, and often that's not appropriate anyway), * Increasing docker build times due to not adding it to .dockerignore, * Ending up in source packages somehow (e.g. serverless framework).
dist-epoch 3y ago
There is a certain quality in simplicity. With inside project venvs what you see is what you get. VS Code can find them, no magic involved. > my laptop only has 2tb and I fill it up With venvs? Even assuming 4 GB pytorch/cuda/whatnot venvs that's a lot of venvs.

by stuaxo 3y ago

globular-toast 3y ago

> The other thing that can't happen is accidentally adding the folder to version control. A few other ways I've seen embedded venvs interfering, off the top of my head: * Polluting output from tools like `find`, `grep` and `tree` (yes, some have .gitignore options, but you have to remember to use them and some don't have the option at all, and often that's not appropriate anyway), * Increasing docker build times due to not adding it to .dockerignore, * Ending up in source packages somehow (e.g. serverless framework).

dist-epoch 3y ago

There is a certain quality in simplicity. With inside project venvs what you see is what you get. VS Code can find them, no magic involved. > my laptop only has 2tb and I fill it up With venvs? Even assuming 4 GB pytorch/cuda/whatnot venvs that's a lot of venvs.