[openstack-dev] [DevStack] Python dependencies: PyPI vs distro packages

Clint Byrum clint at fewbar.com
Tue Aug 6 18:53:38 UTC 2013

Excerpts from Dean Troyer's message of 2013-08-05 10:03:07 -0700:
> * about-face on all-packages to all-PyPI (mtaylor): I'm still on the
> use packages where possible side but DevStack specifically is not in
> the packaging business.  If it were we'd do what Java folk (*sorry*)
> have long taken the approach for non-trivial apps to just include the
> whole damn runtime.  Write once duplicate everywhere.

Just as an FYI, we have gone with the virtualenv + pypi for everything
approach in TripleO. Each project gets its own virtualenv and its own
isolated python path.

This has exposed a few problems (most recently Heat was broken without
at least one thing that pulled in Babel in its virtualenv because it did
not explicitly list Babel in requirements.txt), but these are straight
forward and need fixing anyway.

I was a bit resistant to this approach at first, but this has produced
a very simple system that is also isolated from the python oddities of
any system level tools.

More information about the OpenStack-dev mailing list