is it possible to nest 2 virtualenvs?
I would like to have a base virtualenv and then a more specific virtualenv that accesses all the packages from the base virtualenv and then has its own.
Any hint appreciated, thanks.
is it possible to nest 2 virtualenvs?
I would like to have a base virtualenv and then a more specific virtualenv that accesses all the packages from the base virtualenv and then has its own.
Any hint appreciated, thanks.
You can run in trouble when running python scripts of a virtualenv as subprocesses of another virtualenv. I've found useful to remove from the environment of the subprocess PYTHONPATH and BUILDOUT_ORIGINAL_PYTHONPATH.
No, this isn't currently possible. There is a feature request and a patch for the functionality out there though:
https://github.com/pypa/virtualenv/issues/33