On 10 May 2015 at 07:19, Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2015-05-10 07:09:38 +1200 (+1200), Robert Collins wrote: >> This is my understanding: We explicitly install pip latest in our jobs >> (via get-pip, retrieved over https). Virtualenv shouldn't be version >> sensitive at all to this since its not evaluating versions of >> anything. > > My point was that, because we're running with virtualenv 1.11.4 > currently we end up using pip 1.5.4 which comes bundled within it, > unless the venv itself is explicitly upgraded after creation. It > doesn't use the system-installed pip version we have from get-pip.
Ok, so thats a bug no matter what virtualenv version we're using, because we assume latest pip in all of our other design and impl work :/. We should do the following immediately we create a virtualenv anywhere in our infra: get-pip.py pip install -U wheel setuptools So that we're not running into old-stuff surprises, and so that the pip 7 wheel autobuilding can work. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
