Closed dwpaley closed 2 years ago
For now, set the version of setuptools
to <60
. That's what I did for the 2021.12
release and the nightly package builds.
For now, set the version of
setuptools
to<60
. That's what I did for the2021.12
release and the nightly package builds.
Thanks!
Bump. Hit this again at NERSC. We are pinning the NERSC environments to setuptools<60
as well.
Bump. Encountered this issue on a new Nersc test system. Pinning setuptools<60
solved it.
Alright, this is clearly a headache and is not fixing itself. I’ll look at it next week and try to figure out what’s going on.
Got some clarity on this from @abravalheri. It's apparently well known that importing pip
will break setuptools
because setuptools
packages a modified distutils
while pip
requires the unmodified stdlib distutils
. We can avoid using pip
and setuptools
at the same time, or else export an environment variable SETUPTOOLS_USE_DISTUTILS=stdlib
.
On first glance I only see that pip
is really needed in pkg_utils.require
. @bkpoon any chance we can quarantine calls to require
inside subprocesses so that we don't have to import pip otherwise?
Bump. Encountered this issue on a new Nersc test system. Pinning
setuptools<60
solved it.
In DIALS we got bitten by this and yes
silver-surfer-2 .conda-envs :) [main] $ grep setuptools *
linux.txt:conda-forge::setuptools<60
macos.txt:conda-forge::setuptools<60
windows.txt:conda-forge::setuptools<60
We just pinned setuptools
Recent commits are hitting test failures for
xfel_psana_centos_7 python3.9
on step "Configure and build" with tracebacks that look like this:Traceback
``` Traceback (most recent call last): File "../modules/cctbx_project/libtbx/configure.py", line 34, inIt looks like the same issue discussed in https://github.com/pypa/pip/issues/10742 and https://github.com/pypa/setuptools/issues/2993. I don't have any real idea what's going on, so just flagging this for now.