-
-
Notifications
You must be signed in to change notification settings - Fork 374
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
Issues with CentOS7 and python3 #442
Comments
Hey @jameskirsop. Are you able to provide a PR with a potential fix or one that provides an acceptance test that fails? So we can narrow down the issue. |
@bastelfreak Yep! I actually hacked on together for my environments so I could use the rest of the module. You can review the diff here: jameskirsop@137212f If you think it's PR worthy, I'm happy to create one, but I wasn't sure if it was up-to-scratch. |
That looks okay, can you provide it as a PR? Please don't add |
It seems like #489 has fixed many of these issues, but I'm still having some. In summary, when using the following:
hiera for the group of hosts I'm wanting to deploy a virtualenv to
I'm experiencing the issue described in this StackOverflow post. If I run the suggested resolution:
It would seem that when the virtualenv is set up, some incompatible version of pip is deployed. Some additional info:
Perhaps we should upgrade pip3 on installation of python3, before it's used in a virtualenv? |
Just trying to bump this one up, I've not come up with a suitable way forward yet, but still experiencing issues on CentOS7. Things to factor in:
|
This is a new issue to replace the prematurely closed #303 (as requested by @bastelfreak).
The core of this issue is that a number of combinations of configuration get python/virtualenv/pip3 partially installed, but not one single combination seems to get everything installed.
For example, providing the
version
ofpython34
tries to installpython3-pip
which isn't a valid EPEL package name, and so there's a failure there. This is true for a number of the combinations listed in the original issue (#303).To complicate things a little bit further, EPEL now has a
python36
package, but no matchingpip3
package - installingpip3
requirespython34
to be installed from EPEL.The text was updated successfully, but these errors were encountered: