[issue21496] pyvenv activate_this.py

Attila-Mihaly Balazs added the comment: Hello, A scenario where this would be needed (and where you can't just "execute the script with the python from inside the pyvenv" to get it automatically activate) is when running under mod_wsgi. There sometimes it is needed to activate the virtualenv

[issue21496] pyvenv activate_this.py

Vinay Sajip added the comment: Okay, I'll close this issue. -- resolution: -> not a bug status: open -> closed ___ Python tracker ___ ___

[issue21496] pyvenv activate_this.py

couplewavylines added the comment: "run the command directly...would run with the venv's environment": I'm sorry I didn't realize this, the "You don’t specifically need to activate an environment..." part of the venv docs didn't sink in for me when I read it earlier. So yes, using a subproce

[issue21496] pyvenv activate_this.py

Vinay Sajip added the comment: You say "from other Python code", but you mean running an external command in a subprocess, right? If you know where that command is (which you would need to in order to invoke activate_this on the appropriate venv) then you could run the command directly from it

[issue21496] pyvenv activate_this.py

Changes by Ned Deily : -- nosy: +vinay.sajip ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pytho

[issue21496] pyvenv activate_this.py

New submission from couplewavylines: Is there any plan to add an 'activate_this.py' to venv? The virtualenv package includes this script. Its purpose is to activate the environment "in-place," from other Python code. One use-case is running multiple WSGI apps that each need a different virtual