cloud-init-dev team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

The easiest way to get pip dependencies is through 'tox'.

$ tox -l
py27
py3
pyflakes

$ ./tools/tox-venv py27
(tox:py27)smoser@milhouse:~/src/cloud-init/trunk$ pip list | grep flakes
pyflakes (1.1.0)

You could also use a virtual env and install cloud-init that way. I have a script 'venv' that allows:

$ venv sm-cloud-init pip install .
$ venv sm-cloud-init
(venv:smci)smoser@milhouse:~/src/cloud-init/trunk$ pip list
Cheetah (2.4.4)
cloud-init (0.7.7)
configobj (5.0.6)
Jinja2 (2.8)
jsonpatch (1.13)
jsonpointer (1.10)
Markdown (2.6.6)
MarkupSafe (0.23)
oauthlib (1.1.1)
pip (8.1.1)
pkg-resources (0.0.0)
prettytable (0.7.2)
pyserial (3.0.1)
PyYAML (3.11)
requests (2.10.0)
setuptools (21.0.0)
six (1.10.0)
wheel (0.29.0)

venv can be seen at https://gist.github.com/smoser/2d4100a6a5d230ca937f

I'm not really too interested in having make install pip dependencies if we can just use tox or pip or virtual env.
-- 
https://code.launchpad.net/~paelzer/cloud-init/fixup-test-dependencies/+merge/294203
Your team cloud init development team is requested to review the proposed merge of lp:~paelzer/cloud-init/fixup-test-dependencies into lp:cloud-init.