Add support for installing pip using package manager
et304383 opened this issue · comments
The default installation should always be package where possible.
On Fedora/RHEL, there is a python-pip package which should always be preferred over installing via source/binary.
I'm going to guess most go with source on rhel because the system install is stuck on py2.6 :(
There are ways to override this, by using a different package name. Attributes to control what package is installed is fine.
Installing from source on RHEL by default defeats the purpose of long term stable releases.
Yeah, I'm not saying I agree with the trend. Package installs have been the goals of my PRs too.
On Debian there is also a python-pip package. This cookbook should install it.
This will not be supported. Using https://github.com/poise/poise-python you can make a tiny subclass of one of the existing providers (probably System) that replaces the install_pip logic with the package install of your choice. You might also want to swap out install_setuptools and/or install_virtualenv for distro packages as you see fit. You can use the inversion options framework to make this work even with other peoples' cookbooks so going to close this out.