--
You received this message because you are subscribed to the Google Groups "python-doit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to python-doit...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python-doit/98a8b627-0e20-4d95-b9c4-79ef391ed833n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python-doit/524ae8a1-1bff-4a47-b042-c4b0c0a02088n%40googlegroups.com.
Then you will have to execute everything as scripts ("cmd-action" not as "python-action").
If you directly run a script or the python interpreter from the virtualenv’s bin/ directory (e.g.path/to/ENV/bin/pip
or/path/to/ENV/bin/python-script.py
) thensys.path
will automatically be set to use the Python libraries associated with the virtualenv. But, unlike the activation scripts, the environment variablesPATH
andVIRTUAL_ENV
will not be modified. This means that if your Python script uses e.g. subprocess to run another Python script (e.g. via a!/usr/bin/env
python shebang line) the second script may not be executed with the same Python binary as the first nor have the same libraries available to it. To avoid this happening your first script will need to modify the environment variables in the same manner as the activation scripts, before the second script is executed.
You received this message because you are subscribed to a topic in the Google Groups "python-doit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/python-doit/4Dh2eNtzigg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to python-doit...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/python-doit/524ae8a1-1bff-4a47-b042-c4b0c0a02088n%40googlegroups.com.