-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
CentOS 7 with Python3 does not work #303
Comments
yea, I've hit exactly the same issue, primary use case for me |
+1 Another problem I'm having is that when not using SCL, even after making sure that pip3 is available, I don't see an easy way (either in hiera or otherwise) to have it use a system pip (not SCL or virtualenv) with a different name, e.g., pip3; am I missing something? |
ps - maybe it could have a pip3 provider (similar to puppet's), or some kind of passthrough, vs. trying to figure out whether to use 'pip' or 'pip3'? |
This has been implemented in the fork I'm using/maintaining. https://github.com/xaque208/puppet-python |
Unless I'm missing something, this issue still persists:
gives me a puppet run error: Changing This is on CentOS7 with EPEL repos enabled. Using the manifest example from the docs:
gives me:
Perhaps I'm doing wrong, but I've tried a number of documented and undocumented combinations that seem like they should work, but don't. |
Hey @jameskirsop what do you see when you yum search? Curious to see what epel scl packages you have available . |
@danquack, I can't see where, within this module, that the SCL repos get enabled and I haven't manually installed them.
I'm sure I'd get some SCL packages in Included amongst my current
|
As a follow up, if I set I'm unsure on how #414 resolved the originally reported issue, but surely someone else would have picked up on this problem if it still persisted over the last two years - so I'm at a loss. It would seem that this issue was closed prematurely...? @bastelfreak, as the closer, can you provide some insight? |
This was maybe closed by accident. Can you open a new issue or a PR that adds your code to an acceptance test? |
Setting
python::version
to3
as listed in theparams::valid_versions
doesn't work as the packagepython3
cannot be found. Looking in yum, onlypython34
looks to be valid. If I change thepython::version
to34
(which is not listed as valid), python is installed, but I get a failure trying to installpython3-pip
, as the package does not exist in the the provided epel repo. This seems to me like it would be a common use case for this module. Any suggestions on how I should proceed?The text was updated successfully, but these errors were encountered: