Skip to content
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

how to used pip2.7 as provider in RHEL6 #290

Closed
felipe1982 opened this issue Mar 1, 2016 · 5 comments
Closed

how to used pip2.7 as provider in RHEL6 #290

felipe1982 opened this issue Mar 1, 2016 · 5 comments

Comments

@felipe1982
Copy link

felipe1982 commented Mar 1, 2016

RHEL6 provides python2.6. IUS repo provides python27 and python27-pip packages. The latter provides /usr/bin/pip2.7. How do I get this module to call /usr/bin/pip2.7 for installing python packages?

@jyaworski
Copy link
Member

Based on this code:

https://github.com/stankevich/puppet-python/blob/master/manifests/install.pp#L18-L22

It looks like if you set version to be the prefix (IE python27, etc) it may work.

@stankevich this should probably be laid out explicitly in the docs.

@felipe1982
Copy link
Author

I'm not sure that will work because of silly hard-coded paths ::
https://github.com/stankevich/puppet-python/blob/master/manifests/install.pp#L74

Cheers,
Felipe

On 18 March 2016 at 13:25, Joseph (Jy) Yaworski [email protected]
wrote:

Based on this code:

https://github.com/stankevich/puppet-python/blob/master/manifests/install.pp#L18-L22

It looks like if you set version to be the prefix (IE python27, etc) it
may work.

@stankevich https://github.com/stankevich this should probably be laid
out explicitly in the docs.


You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#290 (comment)

@felipe1982
Copy link
Author

any progress here? I'm stuck using TracyWebTech/puppet-pip until I"m able to use this module to install and utilise pip2.7 on RHEL6

@roqmoyano
Copy link

+1

@michaeljoy
Copy link

Honestly all that needs to happen is the pip_env variable needs to allow you to specify pip2 or pip3 and it would pretty much all work just fine. I just ended up building my own defined class that does what I want instead. Sometimes virtual_env isn't necessary, needed, or wanted for system libraries like boto3 installed in python2 on a box that has both (super common problem)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants