Skip to content

Add support for providing pip provider#412

Closed
danquack wants to merge 4 commits into
voxpupuli:masterfrom
danquack:pip3-support
Closed

Add support for providing pip provider#412
danquack wants to merge 4 commits into
voxpupuli:masterfrom
danquack:pip3-support

Conversation

@danquack
Copy link
Copy Markdown
Contributor

@danquack danquack commented Jul 7, 2018

Pull Request (PR) description

  • Provide the ability to specify which pip provider to utilize. This will allow support for the use of pip3. Currently the syntax only specifies "pip" this will allow the execution to use "pip3"
  • Updated readme to add documentation of how to install anything outside of system python

This Pull Request (PR) fixes the following issues

Fixes #303

@bastelfreak bastelfreak changed the title Added support for providing pip provider Add support for providing pip provider Jul 8, 2018
Comment thread README.md Outdated

**virtualenv** - virtualenv to run pip in. Default: system (no virtualenv)

**pip_provider** - pip provder to execute pip with. Default: pip.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is a tiny typo: provder -> provider

Comment thread manifests/pip.pp Outdated
$pkgname = $name,
$ensure = present,
$virtualenv = 'system',
$pip_proivder = 'pip',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please add a dadatype for this new parameter? An enum would be awesome, otherwise String works as well.

Comment thread manifests/requirements.pp Outdated
define python::requirements (
$requirements = $name,
$virtualenv = 'system',
$pip_provider = 'pip',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, please add a datatype

@bastelfreak bastelfreak added enhancement New feature or request needs-work not ready to merge just yet needs-tests labels Jul 8, 2018
@bastelfreak
Copy link
Copy Markdown
Member

Hi @danquack, thanks for the PR! Can you please take a look at the used email address in your commit? It isn't associated with your github account. Can you also extend the current tests to validate variations of the new parameters?

@bastelfreak
Copy link
Copy Markdown
Member

Hi @danquack,

you can probably fix the rubocop errors with:

 bundle exec rake rubocop:auto_correct

@danquack
Copy link
Copy Markdown
Contributor Author

danquack commented Jul 9, 2018

@bastelfreak copying over to a different fork to consolidate numerous git commits #414

@danquack danquack closed this Jul 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request needs-work not ready to merge just yet tests-fail

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CentOS 7 with Python3 does not work

2 participants