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

Support for Python3.6 executables #420

Closed
pscadiz opened this issue Aug 7, 2018 · 3 comments · Fixed by #489
Closed

Support for Python3.6 executables #420

pscadiz opened this issue Aug 7, 2018 · 3 comments · Fixed by #489

Comments

@pscadiz
Copy link

pscadiz commented Aug 7, 2018

Just leaving a question here.
Am currently experiencing setting up python+virtualenv using python3.6
Have installed it through the epel repositories, which has given the executable /bin/python36

Now setting up virtual environments through python3.6 no longer uses the virtualenv pip package, instead it can be set up using the command /bin/python36 -m venv /path/to/virtualenv.

Here's what I have experienced so far:

  • python::virtualenv does not work because of the exec resource it tries to invoke
  • python::pip, including the virtualenv parameter does not make any change at all

Is there any implementation if the latest version of this module to support it?
Just leaving a question here.

Operating system used - CentOS7
Puppet version - Puppet4
Module version used - v2.1.0 (used the tag)

@bastelfreak
Copy link
Member

Hi @pscadiz.
This is currently not supported. Are you able to provide a PR for this?

@pscadiz
Copy link
Author

pscadiz commented Aug 7, 2018

Hi @bastelfreak

Will work on it, among other things I still owe you :)

Thanks!

@danquack
Copy link
Contributor

Hey @pscadiz, I’m curious if maybe I’m misunderstanding you. But using the rscl libraries I was able able to create a virtual environment and install pip packages, utilizing 2.1. Are you experiencing different? I have this with both CentOS and RHEL. Maybe I can provide how, but just want to make sure I’m understanding you properly.

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

Successfully merging a pull request may close this issue.

3 participants