Brett CannonDec 20, 2022
For those of you who install your virtual environments into a global directory (e.g. virtualenvwrapper users, `$WORKON_HOME`), what's the primary reason you do that instead locally into your workspace (e.g. `.venv` directory next to your code)?
Easy to delete all environments
7.4%
Environment sharing/reuse
24.2%
No reason/habit/tool default
52.6%
Other (w/ follow-up comment to explain)
15.8%
Poll ended at .
Show threadCarlton Gibson 🇪🇺Dec 20, 2022
@brettcannon two reasons: nice to see all the venvs that are around, and I don’t want the venv in the project folder (I have cdvirtualenv and cdsitepackages for the times I do actually want to rummage)
Show threadBrett CannonDec 20, 2022
@carlton What would you think if there was a symlink from `.venv` back to the virtual environment? How about a file that listed the directory of the virtual environment?
Show threadCarlton Gibson 🇪🇺Dec 20, 2022
@brettcannon I’d probably find a symlink noisy, but I’d have no problem at all with a file (a dot file) saying where the venv was. (That would help tools with discovery I’d imagine)
Show threadBrett CannonDec 20, 2022
@carlton That's one of my thoughts on this; see https://fosstodon.org/@brettcannon/109547636668367144 for a discussion I'm having on this very idea.
Show threadCarlton Gibson 🇪🇺Dec 20, 2022

@brettcannon Hmm 404 there right now.

(It's my 🛌 time so I'll check in the morning.)

Thanks.

Show threadBrett Cannon
@carlton If it keeps 404'ing for you, it's a conversation with Simon that came off the poll, so it's easy to find
Dec 20, 2022 at 9:46pmWeb
Show threadCarlton Gibson 🇪🇺Dec 21, 2022
@brettcannon i think the visibility must be set to mentioned only. No worries. I’ll imagine 😜
Show threadBrett CannonDec 21, 2022
@carlton It's basically your suggestion: a file that points to the environment. Toyed with reusing the `.venv` name and `.venv-path`.