Due to changes in the src/pip/_internal/build_env.py handling, the installed patches from patches/patch-src_pip___internal_build__env.py now cause a runtime error due to get_paths() no longer being imported in the installed version of that file.
Either the patch needs to be removed (unclear if this will do what we want based on cursory testing and looking at the rationale behind the removement in the source), or the patch needs to be modified to add
from sysconfig import get_paths
back in. This is related to changes in pypa/pip@da47881 which moved to using src/pip/_internal/locations/_sysconfig.py to find paths. Removing the _distutils_system_mod.py from my local system, uninstalling the pkgsrc pip and installing pip directly using ensurepip seems to work correctly even with multiple versions of python on my system (3.9 and 3.10 tests).
If this others can confirm this new code works for smartos as well, it looks like we could just remove the patch entirely.
Due to changes in the
src/pip/_internal/build_env.pyhandling, the installed patches frompatches/patch-src_pip___internal_build__env.pynow cause a runtime error due toget_paths()no longer being imported in the installed version of that file.Either the patch needs to be removed (unclear if this will do what we want based on cursory testing and looking at the rationale behind the removement in the source), or the patch needs to be modified to add
back in. This is related to changes in pypa/pip@da47881 which moved to using
src/pip/_internal/locations/_sysconfig.pyto find paths. Removing the _distutils_system_mod.py from my local system, uninstalling the pkgsrc pip and installing pip directly usingensurepipseems to work correctly even with multiple versions of python on my system (3.9 and 3.10 tests).If this others can confirm this new code works for smartos as well, it looks like we could just remove the patch entirely.