subject:"\[openstack\-dev\] \[all\]\[requirements\] Why do we use pip install \-U as our install_command"

Re: [openstack-dev] [all][requirements] Why do we use pip install -U as our install_command

2016-02-15 Thread Robert Collins

On 11 February 2016 at 16:09, Clark Boylan wrote: > The reason that I remember off the top of my head is because we spent > far too much time telling people to run `tox -r` when their code failed > during Jenkins testing but ran just fine locally. It removes a > significant

Re: [openstack-dev] [all][requirements] Why do we use pip install -U as our install_command

2016-02-10 Thread Clark Boylan

On Wed, Feb 10, 2016, at 05:46 PM, Tony Breeds wrote: > Hi All, > I confess up front that I'm pretty green in the is area and there is > a lot > of history that I just don't have. That wont stop me from asking/opening > the > discussion. > > As I ask in $subject: why do we install with

[openstack-dev] [all][requirements] Why do we use pip install -U as our install_command

2016-02-10 Thread Tony Breeds

Hi All, I confess up front that I'm pretty green in the is area and there is a lot of history that I just don't have. That wont stop me from asking/opening the discussion. As I ask in $subject: why do we install with --upgrade in our tox environments? Are there issues this is fixing/hiding?