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

2017-07-14 Thread Doug Hellmann
Excerpts from Jeremy Stanley's message of 2017-07-14 16:18:04 +: > On 2017-07-14 16:05:36 + (+), Jesse Pretorius wrote: > > On 7/14/17, 4:54 PM, "Doug Hellmann" wrote: > [...] > > > I wonder if we could convince the PyPA folks to allow get-pip.py > > >to

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

2017-07-14 Thread Jesse Pretorius
On 7/14/17, 5:18 PM, "Jeremy Stanley" 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

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

2017-07-14 Thread Jeremy Stanley
On 2017-07-14 15:55:40 + (+), Jesse Pretorius wrote: > I did a little spelunking to try and figure out where it is we put > pip onto the nodepool nodes. It appears that d-i-b for Ubuntu > Xenial uses packages to put it there, but that doesn’t explain how > the latest version got there.

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

2017-07-14 Thread Jeremy Stanley
On 2017-07-14 16:05:36 + (+), Jesse Pretorius wrote: > On 7/14/17, 4:54 PM, "Doug Hellmann" wrote: [...] > > I wonder if we could convince the PyPA folks to allow get-pip.py > >to take a version argument, so we could specify which version we want in > >our

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

2017-07-14 Thread Jesse Pretorius
On 7/14/17, 4:54 PM, "Doug Hellmann" wrote: > I wonder if we could convince the PyPA folks to allow get-pip.py >to take a version argument, so we could specify which version we want in >our jobs. We would still need a way to manage that version number, but >

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

2017-07-14 Thread Jesse Pretorius
On 7/14/17, 4:17 PM, "Jeremy Stanley" wrote: >Chicken and egg. Once you get to the point where pip can enforce > constraints, you already have a version of setuptools installed. And >as evidenced by, for example, this current bug you would just end up >breaking

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

2017-07-14 Thread Doug Hellmann
Excerpts from Jeremy Stanley's message of 2017-07-14 15:17:52 +: > On 2017-07-14 10:50:50 -0400 (-0400), Doug Hellmann wrote: > > Excerpts from Jesse Pretorius's message of 2017-07-14 08:32:48 +: > > > FYI if you see the following error in your job logs, you have the new > > > setuptools

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

2017-07-14 Thread Jeremy Stanley
On 2017-07-14 10:50:50 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Jesse Pretorius's message of 2017-07-14 08:32:48 +: > > FYI if you see the following error in your job logs, you have the new > > setuptools to thank: > > > > AttributeError: Distribution instance has no attribute

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

2017-07-14 Thread Doug Hellmann
Excerpts from Jesse Pretorius's message of 2017-07-14 08:32:48 +: > FYI if you see the following error in your job logs, you have the new > setuptools to thank: > > AttributeError: Distribution instance has no attribute 'install_requires' > > I’ve registered

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

2017-07-14 Thread Jesse Pretorius
FYI if you see the following error in your job logs, you have the new setuptools to thank: AttributeError: Distribution instance has no attribute 'install_requires' I’ve registered https://github.com/pypa/setuptools/issues/1086 to track the issue, and very quickly got a response and there’s a