Need to branch jujuclient to a tempdir for deploy.py

[Evan]

10:26 AM <vila> ev: deployment failed: ImportError: No module named jujuclient , known issue ?
10:27 AM <ev> vila: yeah, you need to install python-jujuclient. We should get that in a tempdir and PYTHONPATH updated in deploy.py, but hack around it for now by manually installing

[Chris Johnston (cjohnston)]

IIRC we were only branching things that weren't packaged, or the packaged versions weren't helpful (bugs, too old, etc).. If we are going to branch jujuclient, where do we stop? juju-core? Other packages? Having a base set of required packages shouldn't be a problem.

[Evan (ev)]

We branch and pin juju-deployer. It logically follows that we branch and pin its core library.

As the bug points out, you can easily find yourself in the situation where the deploy fails with a confusing error because there's nothing codifying the dependency on jujuclient.

[Andy Doan (doanac)]

This usually happens when someone runs our deploy script from a venv that doesn't have Juju installed into it. I don't know what the best course of action is. I always deploy outside of a venv.

[Vincent Ladeuil (vila)]

@Andy: I was deploying outside of a venv and I had python-jujuclient installed on the host.

[Andy Doan (doanac)]

On 03/03/2014 11:13 AM, Vincent Ladeuil wrote:
> @Andy: I was deploying outside of a venv and I had python-jujuclient
> installed on the host.
n/m - i'm not sure how that would happen then.