B
B
Bjornie2017-05-17 23:56:10
Python
Bjornie, 2017-05-17 23:56:10

Storing all venv in one folder on disk?

I usually create a virtual environment next to the future project, then add the venv folder to .gitignore and work. In principle, it (the folder) does not bother me in any way. However, I recently noticed another option, when all venv are stored somewhere in the 1st folder on the disk, and the project itself is in a completely different place.
Is this way better? More convenient? If not, what is worse / more inconvenient / no difference?
Keeping environments in one folder seems (to me) more organized. All projects in /dev/python/django (for example), and all virtual machines in /venv/myvenv1, /venv/myvenv2, etc.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
sim3x, 2017-05-18
@sim3x

https://virtualenvwrapper.readthedocs.io/en/latest/ A
matter of habit

E
Eugene Zalivadnyi, 2019-03-24
@agnamanshamansky

Virtualenvwrapper is the last century. To manage Python virtual environments, use pipenv , it's more convenient.
I also recommend installing the "fish" (terminal with auto-completion) fish , and so that when you go to the project folder, the environment is automatically activated, put fish-pipenv on top .
If fish is not your case, then in order to monitor and jump between virtual environments created using pipenv (by default they are all in one folder), you can use pipes .
Pipes can be omitted and pipenv can be configured to automatically create .venv inside the project if export PIPENV_VENV_IN_PROJECT=1 is added to the console start settings .

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question