update.py doesn't handle dependencies of configured modules

I'll take a stab at this

I won't say don't do this, but I wonder if the effort wouldn't be better spent just moving things into their own libraries so we can use the existing dependency management tools for installing.

I lost you from "just moving things into their own libraries". Do you have an example?

oslo.config?

https://pypi.python.org/pypi/oslo.config/1.1.0

My concern is that projects like nova use code out of oslo-incubator pretty early. We'll likely never switch over to only using released packages.

Yes, exactly, like with oslo.config.

My understanding was that the plan was to keep the code out of the incubator repository once the first release was stable enough to make a separate library. So nova may use a development version of a library, but not by copying it out of the oslo-incubator.

Oh I understand now. This will just be a quick fix of an inconvenience I recently encountered. I'll abort if it seems too much of an effort.

Sounds good. Like I said, I won't actively block it! :-)

https://review.openstack.org/#/c/26322/

Reviewed: https://review.openstack.org/26322
Committed: http://github.com/openstack/oslo-incubator/commit/e396101c56d997aa8a710cc849ae3dc03cedfdfc
Submitter: Jenkins
Branch: master

commit e396101c56d997aa8a710cc849ae3dc03cedfdfc
Author: Zhongyue Luo <email address hidden>
Date: Mon Apr 8 01:07:47 2013 +0800

    Finds dependencies of configured modules for update.py

    Looks up import lines in the configures modules and finds dependencies.
    Did not load modules since it seemed as an overkill

    Fixes bug #963509

    Change-Id: I690cdf6fb149bbe243add3a35b96f6045ebe10f4