Open Stack

On 2013-09-19 09:24:08 +0800 (+0800), Yongsheng Gong wrote:
[...]
> I upgrade the pip into 1.4.1:
> 
> gongysh at gongysh-ThinkPad-T530:/opt/stack/python-neutronclient$
> .tox/py27/bin/pip install -U pip
> gongysh at gongysh-ThinkPad-T530:/opt/stack/python-neutronclient$
> .tox/py27/bin/pip  --version
> pip 1.4.1 from /mnt/data/opt/stack/python-neutronclient/.tox/py27
> /lib/python2.7/site-packages (python 2.7)
[...]
> Then I run tox -e py27 and it failed:
[...]
> I check the pip version in .tox:
> gongysh at gongysh-ThinkPad-T530:/mnt/data/opt/stack/
> python-neutronclient$  .tox/py27/bin/pip --version
> pip 1.3.1 from /mnt/data/opt/stack/python-neutronclient/.tox/py27
> /lib/python2.7/site-packages/pip-1.3.1-py2.7.egg (python 2.7)
> 
> It is changed back!!!

I've tried to reproduce this and it doesn't seem to happen for me.
Using tox 1.6.1 to run 'tox -e py27' in a current checkout of
python-neutronclient's master branch automatically installs pip
1.4.1 in the virtualenv it creates. Can you try this on another
machine/vm just for confirmation? Clark also suggested on IRC just
now that maybe you have some global tox configuration specifying to
always recreate the virtualenv (essentially -r) and that its
populating it with your system-installed version or perhaps an older
cached download.
-- 
Jeremy Stanley