Open Stack

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.
-- 
Jeremy Stanley