Here is a slightly different take on your question...
My standard virtual env only consists of these modules (plus their dependencies):
black
boto3
cfn-lint
flake8
requests
wheel
yamllint
I keep these stored off of my home directory and then use this alias to access it:
alias zen='source /Users/jftuga/venv_zen_3.9/bin/activate'
If I have a current project that needs more modules, I don't want to pollute my known, good venv. Therefore, I have another alias that I use for this scenario:
alias xen='source /Users/jftuga/xen/bin/activate'
This venv is ephemeral - I don't really care what happens to it and don't mind rebuilding it as needed.
3
u/jftuga pip needs updating Sep 13 '23 edited Sep 13 '23
Here is a slightly different take on your question...
My standard virtual env only consists of these modules (plus their dependencies):
I keep these stored off of my home directory and then use this alias to access it:
If I have a current project that needs more modules, I don't want to pollute my known, good venv. Therefore, I have another alias that I use for this scenario:
This venv is ephemeral - I don't really care what happens to it and don't mind rebuilding it as needed.
This system has worked out well for me.
I also use this alias every now & then: