On 30 Sep, 2009, at 17:31, Gabriel Rossetti wrote:
Ronald Oussoren wrote:Ok, thanks, so from what I understand I only need to activate it if I have to install a package into it.On 25 Sep, 2009, at 14:56, Gabriel Rossetti wrote:Hello everyone,I would like to create a Launchd plist entry to start a virtualenv and run a python project. I created my plist, but I'm not sure how to get it to activate the virtualenv and run the program.Unless you do something special you don't have to activate the virtualenv at all, just make sure that the '#!' line in the script you're starting refers to the python in the virtualenv (instead of having '#!/usr/bin/env python').I have a virtualenv containing a mercurial installation and regularly use the mercurial command-line tools without activating the virtualenv.Ronald
You only have to activate when you need to have executables from the virtualenv on your shell's search-path (that is $PATH). Activating is handy when you are installing software, but is also needed when a script in the virtualenv executes another script in the environment and assumes that that other script is on the search-path.
Ronald
Gabriel
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
