Fix pip at 8.0.0

[mvdbeek]

Since pip seems to be evolving rapidly as of recent.
Otherwise we're getting the import errors on new instances.

[mvdbeek]

@natefoo maybe you have a better idea?

[natefoo]

--no-index --find-links https://wheels.galaxyproject.org/simple/pip should prevent it from installing a newer pip from PyPI (unless that newer version is already installed). This was discussed on IRC today since that's exactly what the case will always be with Travis. The proposed solution is an "always install Galaxy pip even if it's a 'downgrade'" option, although I think we should probably make this the default as long as --no-replace-pip is not specified.

That said, I am not sure if it's possible with pip if you don't specify the exact version as part of pip install as you've done here, which I would prefer not to do because I want to be able to release bug fixes.

[mvdbeek]

@natefoo yep, this was a workaround for travis ... I was first experimenting with downgrading the installed pip to 7.1.2 prior to running tests, but that didn't work. Perhaps the ansible pip module doesn't respect --no-index ?

[natefoo]

Hrm, frustrating, and Ansible hides away the real failure. I believe that version should be 8.0.0+gx1, but hold on a bit, I'm going to make a new 8.0.2+gx1 pip shortly.

[mvdbeek]

Specifying 8.0.0 seems to always catch 8.0.0+gx1, so at least this wouldn't prevent a potential 8.0.0+gx2 to get installed ...

[natefoo]

Ah ok, interesting

[natefoo]

@mvdbeek Can you update it to 8.0.2? I think we're good to go then. You can also drop --pre from the pip args.

[mvdbeek]

@natefoo done, thanks for looking into this!

[natefoo]

Thank you for fixing it!

[natefoo]

Just for the record, this won't be in galaxy.ansible.com until ansible/galaxy-issues#108 is resolved.