[openstack-dev] The danger of capping python-*clients in core projects, and forbidding it in the future
Gareth
academicgareth at gmail.com
Fri Jul 12 03:38:01 UTC 2013
I heard there's a talk about this issue in #openstack-infra last night
(china standard time), what's the conclusion of that?
BTW, how to find meeting log of #openstack-infra? I didn't find it in
http://eavesdrop.openstack.org/
On Thu, Jul 11, 2013 at 11:35 PM, Dirk Müller <dirk at dmllr.de> wrote:
> >> See for example https://bugs.launchpad.net/horizon/+bug/1196823
> > This is arguably a deficiency of mox, which (apparently?) doesn't let us
> mock properties automatically.
>
> I agree, but it is just one example. other test-only issues can happen as
> well.
>
> Similar problem: the *client packages are not self-contained, they
> have pretty strict dependencies on other packages. One case I already
> run into was a dependency on python-requests: newer python-*client
> packages (rightfully) require requests >= 1.x. running those on a
> system that has OpenStack services from Grizzly or Folsom installed
> cause a conflict: there are one or two that require requests to be <
> 1.0.
>
> When you run gating on this scenario, I think the same flipping would
> happen on e.g. requests as well, due to *client or the module being
> installed in varying order.
>
> Greetings,
> Dirk
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
--
Gareth
*Cloud Computing, OpenStack, Fitness, Basketball*
*OpenStack contributor*
*Company: UnitedStack <http://www.ustack.com>*
*My promise: if you find any spelling or grammar mistakes in my email from
Mar 1 2013, notify me *
*and I'll donate $1 or ¥1 to an open organization you specify.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130712/eb0636e5/attachment.html>
More information about the OpenStack-dev
mailing list