summaryrefslogtreecommitdiff
path: root/NOTICE
diff options
context:
space:
mode:
authorMassimiliano Culpo <massimiliano.culpo@gmail.com>2022-06-17 10:42:28 +0200
committerGitHub <noreply@github.com>2022-06-17 10:42:28 +0200
commit667c39987cbe95a4bdac9d3ef887d7e8da625569 (patch)
tree6b7fe1b59a2cfdcc890e7d817ab93f3a9d6934c2 /NOTICE
parentf35d8c41028fe9ab72a7767340f816dc108c5f52 (diff)
downloadspack-667c39987cbe95a4bdac9d3ef887d7e8da625569.tar.gz
spack-667c39987cbe95a4bdac9d3ef887d7e8da625569.tar.bz2
spack-667c39987cbe95a4bdac9d3ef887d7e8da625569.tar.xz
spack-667c39987cbe95a4bdac9d3ef887d7e8da625569.zip
py-setuptools: install setuptools from wheels directly (#31131)
When installing setuptools from sources in Spack, we might get into weird failures due to the way we use pip. In particular, for Spack it's necessary to install in a non-isolated pip environment to allow using PYTHONPATH as a selection method for all the build requirements of a Python package. This can fail when installing setuptools since there might be a setuptools version already installed for the Python interpreter being used, with different entry points than the one we want to install. Installing from wheels both pip and setuptools should harden our installation procedure in the context of: - Bootstrapping Python dependencies of Spack - Using external Python packages
Diffstat (limited to 'NOTICE')
0 files changed, 0 insertions, 0 deletions