[openstack-dev] unable to run tox due to the '--pre' argument

[Yongsheng Gong]

Hi,
I tried to run tests after I changed some codes in python neutron client,
But I failed.
Could someone please help me out?

$ tox -e py27
GLOB sdist-make: /mnt/data/opt/stack/python-neutronclient/setup.py
py27 create: /mnt/data/opt/stack/python-neutronclient/.tox/py27
py27 installdeps:
-r/mnt/data/opt/stack/python-neutronclient/requirements.txt,
-r/mnt/data/opt/stack/python-neutronclient/test-requirements.txt
ERROR: invocation failed, logfile:
/mnt/data/opt/stack/python-neutronclient/.tox/py27/log/py27-1.log
ERROR: actionid=py27
msg=getenv
cmdargs=[local('/mnt/data/opt/stack/python-neutronclient/.tox/py27/bin/pip'),
'install', '--pre',
'-r/mnt/data/opt/stack/python-neutronclient/requirements.txt',
'-r/mnt/data/opt/stack/python-neutronclient/test-requirements.txt']
...
Usage:
  pip install [options]  ...
  pip install [options] -r  ...
  pip install [options] [-e]  ...
  pip install [options] [-e]  ...
  pip install [options]  ...

no such option: --pre

ERROR: could not install deps
[-r/mnt/data/opt/stack/python-neutronclient/requirements.txt,
-r/mnt/data/opt/stack/python-neutronclient/test-requirements.txt]


$ tox --version
1.6.1 imported from /usr/local/lib/python2.7/dist-packages/tox/__init__.pyc
$ pip --version
pip 1.4.1 from /usr/local/lib/python2.7/dist-packages/pip-1.4.1-py2.7.egg
(python 2.7)

$ cat /etc/issue
Ubuntu 13.04 \n \l

Regards,
Yong Sheng Gong
UnitedStack Inc.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] unable to run tox due to the '--pre' argument

[Jeremy Stanley]

On 2013-09-19 08:12:47 +0800 (+0800), Yongsheng Gong wrote:
[...]
> $ tox -e py27
[...]
> no such option: --pre
[...]
> $ tox --version
> 1.6.1 imported from /usr/local/lib/python2.7/dist-packages/tox/
> __init__.pyc
> $ pip --version
> pip 1.4.1 from /usr/local/lib/python2.7/dist-packages/
> pip-1.4.1-py2.7.egg (python 2.7)
[...]

You may have an existing .tox/py27 virtualenv with an earlier
version of pip already installed and tox is reusing it. Running
'.tox/py27/bin/pip --version' should tell you. If you pass the -r
switch to tox when running like 'tox -e py27 -r' it should clear any
existing virtualenv and create a fresh one, or you can upgrade the
pip inside it with '.tox/py27/bin/pip install -U pip' if you want.
-- 
Jeremy Stanley

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] unable to run tox due to the '--pre' argument

[Yongsheng Gong]

Thanks for the reply.

It is weird the pip will be changed into 1.3.1 after I run tox -e py27.
Here is the process I run:

gongysh@gongysh-ThinkPad-T530:/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)

I upgrade the pip into 1.4.1:

gongysh@gongysh-ThinkPad-T530:/opt/stack/python-neutronclient$
.tox/py27/bin/pip install -U pip
gongysh@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)
gongysh@gongysh-ThinkPad-T530:/opt/stack/python-neutronclient/.tox/py27/lib/python2.7/site-packages$
ls
easy-install.pth  pip  pip-1.4.1-py2.7.egg-info
 setuptools-0.6c11-py2.7.egg  setuptools.pth

Then I run tox -e py27 and it failed:

gongysh@gongysh-ThinkPad-T530:/mnt/data/opt/stack/python-neutronclient$ tox
-e py27
GLOB sdist-make: /mnt/data/opt/stack/python-neutronclient/setup.py
py27 create: /mnt/data/opt/stack/python-neutronclient/.tox/py27
py27 installdeps:
-r/mnt/data/opt/stack/python-neutronclient/requirements.txt,
-r/mnt/data/opt/stack/python-neutronclient/test-requirements.txt
ERROR: invocation failed, logfile:
/mnt/data/opt/stack/python-neutronclient/.tox/py27/log/py27-1.log
ERROR: actionid=py27
msg=getenv
cmdargs=[local('/mnt/data/opt/stack/python-neutronclient/.tox/py27/bin/pip'),
'install', '--pre',
'-r/mnt/data/opt/stack/python-neutronclient/requirements.txt',
'-r/mnt/data/opt/stack/python-neutronclient/test-requirements.txt']

I check the pip version in .tox:
gongysh@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!!!

Regards,
Yong Sheng Gong


On Thu, Sep 19, 2013 at 9:02 AM, Jeremy Stanley  wrote:

> On 2013-09-19 08:12:47 +0800 (+0800), Yongsheng Gong wrote:
> [...]
> > $ tox -e py27
> [...]
> > no such option: --pre
> [...]
> > $ tox --version
> > 1.6.1 imported from /usr/local/lib/python2.7/dist-packages/tox/
> > __init__.pyc
> > $ pip --version
> > pip 1.4.1 from /usr/local/lib/python2.7/dist-packages/
> > pip-1.4.1-py2.7.egg (python 2.7)
> [...]
>
> You may have an existing .tox/py27 virtualenv with an earlier
> version of pip already installed and tox is reusing it. Running
> '.tox/py27/bin/pip --version' should tell you. If you pass the -r
> switch to tox when running like 'tox -e py27 -r' it should clear any
> existing virtualenv and create a fresh one, or you can upgrade the
> pip inside it with '.tox/py27/bin/pip install -U pip' if you want.
> --
> Jeremy Stanley
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] unable to run tox due to the '--pre' argument

[Jeremy Stanley]

On 2013-09-19 09:24:08 +0800 (+0800), Yongsheng Gong wrote:
[...]
> I upgrade the pip into 1.4.1:
> 
> gongysh@gongysh-ThinkPad-T530:/opt/stack/python-neutronclient$
> .tox/py27/bin/pip install -U pip
> gongysh@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@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

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] unable to run tox due to the '--pre' argument

[Zhongyue Luo]

Looks like this problem happens in systems that use pip<1.4 but upgraded
tox to 1.6.1

http://tox.readthedocs.org/en/latest/config.html#confval-install_command=ARGV


On Fri, Sep 20, 2013 at 12:47 AM, Jeremy Stanley  wrote:

> On 2013-09-19 09:24:08 +0800 (+0800), Yongsheng Gong wrote:
> [...]
> > I upgrade the pip into 1.4.1:
> >
> > gongysh@gongysh-ThinkPad-T530:/opt/stack/python-neutronclient$
> > .tox/py27/bin/pip install -U pip
> > gongysh@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@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
>
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
*Intel SSG/STOD/DCST/CIT*
880 Zixing Road, Zizhu Science Park, Minhang District, 200241, Shanghai,
China
+862161166500
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] unable to run tox due to the '--pre' argument

[Monty Taylor]

On 09/23/2013 12:14 AM, Zhongyue Luo wrote:
> Looks like this problem happens in systems that use pip<1.4 but upgraded
> tox to 1.6.1
> 
> http://tox.readthedocs.org/en/latest/config.html#confval-install_command=ARGV

Yes. We have been rolling out tox.ini changes to projects. I'll push one
up for neutronclient right now...

https://review.openstack.org/47848

This change should essentially be ported in to all projects. I'm getting
to it slowly, but if other people want to step up and do that too, I'd
welcome the help!

> On Fri, Sep 20, 2013 at 12:47 AM, Jeremy Stanley  > wrote:
> 
> On 2013-09-19 09:24:08 +0800 (+0800), Yongsheng Gong wrote:
> [...]
> > I upgrade the pip into 1.4.1:
> >
> > gongysh@gongysh-ThinkPad-T530:/opt/stack/python-neutronclient$
> > .tox/py27/bin/pip install -U pip
> > gongysh@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@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
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> 
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> 
> 
> 
> -- 
> *Intel SSG/STOD/DCST/CIT*
> 880 Zixing Road, Zizhu Science Park, Minhang District, 200241, Shanghai,
> China
> +862161166500
> 
> 
> ___
> OpenStack-dev mailing list
> OpenStack-dev@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev