Open Stack

On Fri, 2012-11-23 at 11:55 +0100, Thierry Carrez wrote:
> There seem to be two options there: just push everything on the same
> PyPI module, or have multiple PyPI modules for each series. I'd say
> the latter looks worse.

I don't really buy that unstable development releases of Oslo have to go
to PyPI in order for core projects to be able to consume them.

pip supports http:// URLs of tarballs. Why not use that during
development?

> For the former, I suspect you can specify ">=1.2.1 <2" as far as
> dependencies are concerned.

I really, really hate version caps like that :)

Say we add a new API to oslo-config, release version 1.2.1 and nova
wants to express that it requires that API. Why on earth would we say
that this version of nova is incompatible with version 2.x of
oslo-config?

In another context, Monty's case for this kind of version capping is
that you can't depend on Python library maintainers to have any
discipline around API stability - but that's exactly the discipline
we're aiming for with Oslo!

Cheers,
Mark.