You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Newer versions of pip implement PEP668 support, which will soon be enabled default (TL;DR, it will fail to install packages to system-managed Python environments, on which ansible-builder relies heavily).
Switching to virtual environments in EEs is not really an option for the short-medium term anyway; we need to continue to assume the ability to install any and all necessary packages in the system Python environment.
Luckily it should be an easy fix; we just need to ensure we're setting PIP_BREAK_SYSTEM_PACKAGES=1 in the environment for on all of builder's pip invocations; there shouldn't be any consequence to setting this for older pip versions, and it'll keep new ones functioning.
The text was updated successfully, but these errors were encountered:
Newer versions of
pip
implement PEP668 support, which will soon be enabled default (TL;DR, it will fail to install packages to system-managed Python environments, on which ansible-builder relies heavily).Switching to virtual environments in EEs is not really an option for the short-medium term anyway; we need to continue to assume the ability to install any and all necessary packages in the system Python environment.
Luckily it should be an easy fix; we just need to ensure we're setting
PIP_BREAK_SYSTEM_PACKAGES=1
in the environment for on all of builder'spip
invocations; there shouldn't be any consequence to setting this for older pip versions, and it'll keep new ones functioning.The text was updated successfully, but these errors were encountered: