Skip to content

Pip3 is called explicitly #236

@WillDyson

Description

@WillDyson

The pip3 binary is referred to directly in the playbook.
RHEL doesn't automatically link Pip 3.8 to this name as there may be multiple versions of Python 3 installed.
Are we able to remove this requirement or parametrise it somehow?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions