[openstack-dev] [all] New setuptools release, and the world is broken

Jesse Pretorius 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
>    anyway.

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 [1] so that tox uses them when building virtualenvs. Another option could be to use a configuration file [2] to specify a directory to find the right wheels in.

[1] https://virtualenv.pypa.io/en/stable/userguide/#the-extra-search-dir-option
[2] https://virtualenv.pypa.io/en/stable/reference/#configuration-file

Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse at rackspace.com and delete the original message. Your cooperation is appreciated.

More information about the OpenStack-dev mailing list