On 5 November 2015 at 07:37, Sean Dague <[email protected]> wrote: > It only really will screw when upper-constraints.txt gets updated on a > branch.
Bah, yes. > I honestly think it's ok to not be perfect here. In the base case we'll > speed up a good chunk, and we'll be slower (though not as slow as today) > for a day after we bump upper-constraints for something expensive (like > numpy). It seems like a reasonable trade off for not much complexity. Oh, I clearly wasn't clear. I think your patch is a good thing. I'm highlighting the corner case and proposing a down-the-track way to address it. And the reason I'm doing that is that Clark has said that we have lots and lots of trouble updating images, so I'm expecting the corner case to be fairly common :/. -Rob -- Robert Collins <[email protected]> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
