-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix pip at 8.0.0 #9
Conversation
@natefoo maybe you have a better idea? |
That said, I am not sure if it's possible with pip if you don't specify the exact version as part of |
@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 |
Hrm, frustrating, and Ansible hides away the real failure. I believe that version should be |
Specifying |
Ah ok, interesting |
@mvdbeek Can you update it to |
@natefoo done, thanks for looking into this! |
Thank you for fixing it! |
Just for the record, this won't be in galaxy.ansible.com until ansible/galaxy-issues#108 is resolved. |
Since pip seems to be evolving rapidly as of recent.
Otherwise we're getting the import errors on new instances.