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.

Sign up for GitHub

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

Jump to bottom

Pip3 is called explicitly #236

Open
WillDyson opened this issue Jun 11, 2024 · 0 comments
Open

Pip3 is called explicitly #236

WillDyson opened this issue Jun 11, 2024 · 0 comments

Comments

@WillDyson
Copy link
Contributor

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?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@WillDyson