No. The environment as changed by virtualenv is copied for the new process and is not altered from the outside after that.
BTW, you don't need to activate a virtualenv in order to use it to start a process. It is sufficient to use the env's python interpreter (by using it's full path like /path_to_venv/bin/python
)—and maybe set additional environment variables beforehand—to start your process.