ModuleNotFoundError: No module named 'setuptools.command.test'

[yu-iskw]

Overview

I got the similar error ModuleNotFoundError: No module named 'setuptools.command.test' with the install command on GitHub Actions as the benchmarks workflow was failed.

error: Failed to prepare distributions
  Caused by: Failed to fetch wheel: logbook==1.5.3
  Caused by: Failed to build: `logbook==1.5.3`
  Caused by: Build backend failed to determine extra requires with `build_wheel()` with exit status: 1
--- stdout:
--- stderr:
Traceback (most recent call last):
  File "<string>", line 14, in <module>
  File "/home/runner/.cache/uv/builds-v0/.tmp6kYDCi/lib/python3.11/site-packages/setuptools/build_meta.py", line 327, in get_requires_for_build_wheel
    return self._get_build_requires(config_settings, requirements=[])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/runner/.cache/uv/builds-v0/.tmp6kYDCi/lib/python3.11/site-packages/setuptools/build_meta.py", line 297, in _get_build_requires
    self.run_setup()
  File "/home/runner/.cache/uv/builds-v0/.tmp6kYDCi/lib/python3.11/site-packages/setuptools/build_meta.py", line 497, in run_setup
    super().run_setup(setup_script=setup_script)
  File "/home/runner/.cache/uv/builds-v0/.tmp6kYDCi/lib/python3.11/site-packages/setuptools/build_meta.py", line 313, in run_setup
    exec(code, locals())
  File "<string>", line 64, in <module>
ModuleNotFoundError: No module named 'setuptools.command.test'

The failed benchmarks workflow

https://github.com/astral-sh/uv/actions/runs/10137169832/job/28027028298

error: Failed to download and build `pyhive==0.7.0`
  Caused by: Failed to build: `pyhive==0.7.0`
  Caused by: Build backend failed to determine extra requires with `build_wheel()` with exit status: 1
--- stdout:

--- stderr:
Traceback (most recent call last):
  File "<string>", line 14, in <module>
  File "/home/runner/work/uv/uv/.cache/builds-v0/.tmpuS9Fnv/lib/python3.10/site-packages/setuptools/build_meta.py", line 327, in get_requires_for_build_wheel
    return self._get_build_requires(config_settings, requirements=[])
  File "/home/runner/work/uv/uv/.cache/builds-v0/.tmpuS9Fnv/lib/python3.10/site-packages/setuptools/build_meta.py", line 297, in _get_build_requires
    self.run_setup()
  File "/home/runner/work/uv/uv/.cache/builds-v0/.tmpuS9Fnv/lib/python3.10/site-packages/setuptools/build_meta.py", line 497, in run_setup
    super().run_setup(setup_script=setup_script)
  File "/home/runner/work/uv/uv/.cache/builds-v0/.tmpuS9Fnv/lib/python3.10/site-packages/setuptools/build_meta.py", line 313, in run_setup
    exec(code, locals())
  File "<string>", line 4, in <module>
ModuleNotFoundError: No module named 'setuptools.command.test'

[bardiharborow]

setuptools 72.0.0 (released 3 hours ago) has caused certain Python packages to break (pypa/setuptools#4519). This is compounded by uv's installation of the latest version of setuptools during venv setup.

[hauntsaninja]

This isn't uv's fault. See pypa/setuptools#4519 (comment) , but use UV_CONSTRAINT env var instead

Edit: oops, UV_CONSTRAINT doesn't actually work the same way, see #5551 (comment)

[yu-iskw]

@hauntsaninja Thank you for the help. That works! Let me close the issue.

[hauntsaninja]

I'd still be interested if any uv folks have ideas for how to improve reproducibility of isolated build envs.

Here's one (probably dumb) suggestion. uv pip install -c constraints.txt ... should apply the constraints to isolated build environments as well. Even if not dumb, maybe too much of a departure from pip though...

[delfick]

it seems that UV_CONSTRAINT or --constraint flag isn't working to restrict the version that uv uses

Using this as setuptools-constraint.txt

setuptools==70.3.0

Seems uv still uses the latest setuptools

╰─ ./tools/uv pip install envparse --constraint setuptools-constraint.txt -v
Audited 1 package in 55ms
DEBUG uv 0.2.29
DEBUG Searching for Python interpreter in system path
DEBUG Found `cpython-3.10.14-macos-aarch64-none` at `/Users/stephen.moore/.virtualenvs/kraken4/bin/python3` (active virtual environment)
DEBUG Using Python 3.10.14 environment at /Users/stephen.moore/.virtualenvs/kraken4/bin/python3
DEBUG Acquired lock for `/Users/stephen.moore/.virtualenvs/kraken4`
DEBUG At least one requirement is not satisfied: envparse
DEBUG Using request timeout of 30s
DEBUG Solving with installed Python version: 3.10.14
DEBUG Adding direct dependency: envparse*
DEBUG No cache entry for: https://pypi.org/simple/envparse/
DEBUG Searching for a compatible version of envparse (*)
DEBUG Selecting: envparse==0.2.0 [compatible] (envparse-0.2.0.tar.gz)
DEBUG Acquired lock for `/Users/stephen.moore/Library/Caches/uv/built-wheels-v3/pypi/envparse/0.2.0`
DEBUG No cache entry for: https://files.pythonhosted.org/packages/2f/8d/bee8a59732c169a455627ff1557d0db180f7c352b0274480267ad3e46875/envparse-0.2.0.tar.gz
DEBUG Downloading source distribution: envparse==0.2.0
DEBUG Preparing metadata for: envparse==0.2.0
DEBUG No static `PKG-INFO` available for: envparse==0.2.0 (PkgInfo(UnsupportedMetadataVersion("1.1")))
DEBUG No static `pyproject.toml` available for: envparse==0.2.0 (MissingPyprojectToml)
INFO Ignoring empty directory
DEBUG Solving with installed Python version: 3.10.14
DEBUG Adding direct dependency: setuptools>=40.8.0
DEBUG No cache entry for: https://pypi.org/simple/setuptools/
DEBUG Searching for a compatible version of setuptools (>=40.8.0)
DEBUG Selecting: setuptools==72.0.0 [compatible] (setuptools-72.0.0-py3-none-any.whl)
DEBUG No cache entry for: https://files.pythonhosted.org/packages/2f/83/06edd551b4fdf6170dcbafeeed588a8909819e943905c182ebdc98835be8/setuptools-72.0.0-py3-none-any.whl.metadata
DEBUG Tried 1 versions: setuptools 1
DEBUG Split specific environment resolution took 0.181s
DEBUG Installing in setuptools==72.0.0 in /Users/stephen.moore/Library/Caches/uv/builds-v0/.tmpn7RJ3U
DEBUG Identified uncached requirement: setuptools==72.0.0
DEBUG Downloading and building requirement for build: setuptools==72.0.0
DEBUG No cache entry for: https://files.pythonhosted.org/packages/2f/83/06edd551b4fdf6170dcbafeeed588a8909819e943905c182ebdc98835be8/setuptools-72.0.0-py3-none-any.whl
DEBUG Installing build requirement: setuptools==72.0.0
DEBUG Calling `setuptools.build_meta:__legacy__.get_requires_for_build_wheel()`
error: Failed to download and build `envparse==0.2.0`
  Caused by: Failed to build: `envparse==0.2.0`
  Caused by: Build backend failed to determine extra requires with `build_wheel()` with exit status: 1
--- stdout:

--- stderr:
Traceback (most recent call last):
  File "<string>", line 14, in <module>
  File "/Users/stephen.moore/Library/Caches/uv/builds-v0/.tmpn7RJ3U/lib/python3.10/site-packages/setuptools/build_meta.py", line 327, in get_requires_for_build_wheel
    return self._get_build_requires(config_settings, requirements=[])
  File "/Users/stephen.moore/Library/Caches/uv/builds-v0/.tmpn7RJ3U/lib/python3.10/site-packages/setuptools/build_meta.py", line 297, in _get_build_requires
    self.run_setup()
  File "/Users/stephen.moore/Library/Caches/uv/builds-v0/.tmpn7RJ3U/lib/python3.10/site-packages/setuptools/build_meta.py", line 497, in run_setup
    super().run_setup(setup_script=setup_script)
  File "/Users/stephen.moore/Library/Caches/uv/builds-v0/.tmpn7RJ3U/lib/python3.10/site-packages/setuptools/build_meta.py", line 313, in run_setup
    exec(code, locals())
  File "<string>", line 4, in <module>
ModuleNotFoundError: No module named 'setuptools.command.test'
---

[hauntsaninja]

Oops, so it is:

λ cat c.in
setuptools<70

λ PIP_CONSTRAINT=c.in pip install moviepy --no-cache-dir
...
Installing collected packages: moviepy
...
Successfully installed moviepy-1.0.3

λ uv pip uninstall moviepy --system                     
Uninstalled 1 package in 21ms
 - moviepy==1.0.3

λ UV_CONSTRAINT=c.in PIP_CONSTRAINT=c.in uv pip install moviepy --system
⠹ moviepy==1.0.3                                                                                                                                                            error: Failed to download and build `moviepy==1.0.3`
  Caused by: Failed to build: `moviepy==1.0.3`
  Caused by: Build backend failed to determine extra requires with `build_wheel()` with exit status: 1
--- stdout:

--- stderr:
Traceback (most recent call last):
  File "<string>", line 14, in <module>
  File "/root/.cache/uv/builds-v0/.tmp06f83o/lib/python3.11/site-packages/setuptools/build_meta.py", line 327, in get_requires_for_build_wheel
    return self._get_build_requires(config_settings, requirements=[])
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/.cache/uv/builds-v0/.tmp06f83o/lib/python3.11/site-packages/setuptools/build_meta.py", line 297, in _get_build_requires
    self.run_setup()
  File "/root/.cache/uv/builds-v0/.tmp06f83o/lib/python3.11/site-packages/setuptools/build_meta.py", line 497, in run_setup
    super().run_setup(setup_script=setup_script)
  File "/root/.cache/uv/builds-v0/.tmp06f83o/lib/python3.11/site-packages/setuptools/build_meta.py", line 313, in run_setup
    exec(code, locals())
  File "<string>", line 21, in <module>
NameError: name 'TestCommand' is not defined
---

(same deal with e.g. vcrpy)

@yu-iskw could you re-open?

[yu-iskw]

@hauntsaninja @delfick Indeed I didn't solve the issue only with UV_CONSTRAINTS and --no-build-isolation. In my case, I needed to add the dependency on wheel as below. I mainly use uv in GitHub Actions. As I install dependencies to system with uv in GitHub Action, I have the same requirements file to set up the basics to use uv and run a uv pip install command.

1. Run python -m pip install --no-cache -r requirements-setup.txt
2. Run python -m uv pip install ... with UV_CONSTRAINTS=path/to/requirements-setup.txt.

# requirements-setup.txt
pip==24.2
setuptools==71.0.0
wheel>=0.40,<1.0
uv>=0.2,<0.3

[delfick]

if you do a uv cache clean and do it again, does it still work?

Cause adding those extra things to the constraints doesn't make a difference for me

[weihenglim]

Using the --no-build-isolation flag works for me (uv correctly uses the installed version of setuptools)