Administered by:
What are people's preferred tools for virtual environment management these days? I specifically care about being able to have hundreds of different project folders each with their own environment
I've been using pipenv for years despite not using Pipfiles - what else should I be considering in 2024?
I want a maximum of one command (equivalent to "pipenv shell") that I have to run in a directory in order to activate the corresponding environment
@simon I use virtualenvwrapper. workon [project name] moves me to the project dir and activates the env. Envs are in ~/.envs. I've also set pip to not allow installing outside an env.
I'm considering using uv, but I don't think it will stop me using virtualenvwrapper.
Happy to share my config if it helps
@simon by the way, I use virtualenvwrapper even with pipenv projects. That is, if I'm using a project that does use pipenv, I'll still make the env manually. This might be missing the point of pipenv, but it does mean everything is consistent