[openstack-dev] [all] New setuptools release, and the world is broken
Jesse.Pretorius at rackspace.co.uk
Fri Jul 14 16:43:44 UTC 2017
On 7/14/17, 5:18 PM, "Jeremy Stanley" <fungi at yuggoth.org> wrote:
> Is there a mechanism to leverage this in tox or when invoking
> virtualenv? We don't run get-pip.py in most jobs because our images
> have pip/setuptools preinstalled to get around bootstrapping issues,
> though I suppose that could with some effort be moved into job
> runtime as a (very early) builder macro. Using constraints to
> control these during image generation doesn't make a whole lot of
> sense though as images are only rebuilt once a day and so tracking
> these in the constraints list won't be self-testing in that regard
Fair enough, although that’s what we have today so I don’t see it as worse. In fact, I think it’s an improvement because our constraints can be updated when we choose to (through the normal requirements management process) rather than whenever the new package releases.
I think it may make sense to do a pre-tox macro which preps pip/setuptools/wheel using get-pip.py, then places the relevant wheels into the virtualenv_support directory  so that tox uses them when building virtualenvs. Another option could be to use a configuration file  to specify a directory to find the right wheels in.
More information about the OpenStack-dev