Skip to content

Support for Python3.6 executables #420

@pscadiz

Description

@pscadiz

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions