Open WillDyson opened 3 months ago
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?
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?