Issue #17030 has been updated by Adrien Thebo.
I spoke with Jeff about this and the preferred resolution is to try pip if it's available and then fall back to pip-python on Redhat. On other platforms we just just probe for pip. In addition it might be worthwhile to check the pip version to ensure that we're getting the python pip instead of the perl pip. ---------------------------------------- Bug #17030: pip provider should handle multiple pips/pythons https://projects.puppetlabs.com/issues/17030#change-83703 Author: Bradley Kreider Status: Needs More Information Priority: Normal Assignee: Category: provider Target version: Affected Puppet version: 2.6.17 Keywords: Branch: https://github.com/puppetlabs/puppet/pull/1486 The Pip provider should provide a way to specify the path to pip. This would allow people to manage multiple python installs, by point to the one they want to install into. In RHEL, this makes it easy to have a non-system python installed somewhere (ie: 2.7 or 3.x) and let puppet manage the python packages. This is related to bug #15980. (related in the way that if you could provide the path to the pip binary, 15980 would have a workaround). -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
