Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-1082

pip provider should handle multiple pips/pythons

    XMLWordPrintable

    Details

    • Template:
      PUP Bug Template
    • Team:
      Night's Watch
    • Sprint:
      PR - 2019-04-17, PR - 2019-05-02, PR - 2019-05-15, PR - 2019-05-29, PR - 2019-06-12
    • Zendesk Ticket IDs:
      35155
    • Zendesk Ticket Count:
      1
    • Release Notes:
      Enhancement
    • Release Notes Summary:
      Hide
      Added the possibility for providers to implement targetable package command for pip and pip3. This allows adding a custom path to pip/pip3.

      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
      Show
      Added the possibility for providers to implement targetable package command for pip and pip3. This allows adding a custom path to pip/pip3. 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

      Description

      The Pip provider should provide a way to specify the path to pip. This would allow people to manage multiple python installs, by pointing 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).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              sebastian.miclea Sebastian Miclea
              Reporter:
              redmine.exporter redmine.exporter
              QA Contact:
              Narmadha Perumal
              Votes:
              8 Vote for this issue
              Watchers:
              14 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support