> Use virtualenv to create a local python, and activate that when > developing for that branch. Thanks for the suggestion, but that's the problem: having to activate it. Isn't there some way to simply have the local script look at a specified dir rather than starting a virtual environment? -T