3 ms·
> things get tricky when it comes to nested venvs Never had such a requirement. Environments, like the interpreter itself, seem a singleton concept. I have
by smitty1e 6y ago
> things get tricky when it comes to nested venvs
Never had such a requirement.
Environments, like the interpreter itself, seem a singleton concept.
I have used a Makefile that sources different Bash environment variables kept in files in etc/ within the venv to switch between, say, a Flask and a Gunicorn startup.
- raverbashing 6y agoYes you're using nested venvs you're really making it harder on yourself. Way way harder on yourself.
- smitty1e 6y agoI've used a nested git repository, with the child directory in the .gitignore of the parent. I know that there is some thing about installing git checkouts with pip, but that has not been important to me yet.
- teitoklien 6y agoWhy not just use git submodules feature ?
- ajford 6y agoI honestly can't even come up with a valid reason for something like nested venvs. At that point it seems more like someone's doing something wrong than 'things get tricky'.
- beojan 6y agoIf you have unlimited disk space, sure. Otherwise, it would be really nice to be able to layer venvs so you don't need to have multiple copies of a package installed.
- paulie_a 6y agoIf anything it just simply seems like a dumb idea to do so. Virtualenv is simple and works really nicely. Why anyone would want to add unnecessary complexity is beyond me