It seems that their package is broken. This is because in setup.py they are doing

from setuptools.command.test import test as TestCommand

but setuptools.command.test was removed on 28 Jul 2024 (yesterday):
https://setuptools.pypa.io/en/stable/history.html#v72-0-0

Here’s a similar issue on the official GitHub repo: https://github.com/pypa/setuptools/issues/4519

To solve it locally do one of the following:

• downgrade your setuptools as @reza.safiyat suggested;
• use a project manager (like Poetry or Hatch) and pin setuptools = "<72.0.0".

UPDATE

setuptools 72.0.0 has been yanked (https://pypi.org/project/setuptools/72.0.0/#history) and the removal of command.test has been postponed to November 15.

Everything should work as it did yesterday (with the addition of a new big warning, hopefully).

This module was removed from in this commit.

Using setuptools<72.0.0 will alleviate this problem.

Steps you may use once you have sourced the relevant python environment:

# Install setuptools below v72.0.0. Add `-U` after `install` in case you want to upgrade to a version below 72.0.0, if you already have setuptools installed.
python -m pip install 'setuptools<72.0.0'
# Install RandomWords.
python -m pip install RandomWords

Edit

setuptools 72.0.0 has been yanked

https://pypi.org/project/setuptools/72.0.0/#history

Rerun your pipelines all good now.

This bug arises from changes made to setuptools.command.test in the 72.0.0 update of setuptools. For more details, refer to the setuptools · PyPI page. One of the dependencies used in this repository, Ch00k/ffmpy: Pythonic interface for FFmpeg/FFprobe command line, utilizes setuptools.command.test.

As a temporary solution, I forked the project and removed the relevant code to ensure it runs smoothly. You can use the following command to install the modified version:

pip install git+https://github.com/EuDs63/ffmpy.git

https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/16289#issuecomment-2255106490

option 2

RUN pip3 install -I --force-reinstall setuptools==71.0.0
RUN pip3 install --no-build-isolation --no-cache-dir -r requirements.txt

https://github.com/pypa/setuptools/issues/4519#issuecomment-2255358015

option 3

RUN echo "setuptools<72" > constraints.txt

ENV PIP_CONSTRAINT=constraints.txt

RUN poetry config virtualenvs.create false && 
    poetry run pip install sqlalchemy==1.3.24 && 
    poetry install --no-cache && 

https://github.com/pypa/setuptools/issues/4519#issuecomment-2255446798

option 4

pip3 install --no-build-isolation --no-cache-dir "setuptools<72"

Package version v72.0.0 has just been yanked (https://pypi.org/project/setuptools/72.0.0/).

If you replay your pipelines, the error should no longer pop up.

I’ve got this error too in my Dockerfile.

Workaround:

RUN echo "setuptools<72" > constraints.txt

ENV PIP_CONSTRAINT=constraints.txt

RUN poetry config virtualenvs.create false && 
    poetry run pip install sqlalchemy==1.3.24 && 
    poetry install --no-cache && 

I could not understand why when I degraded the setuptools to version below 72.0.0 it kept cruising with the error of ModuleNotFoundError: No module named 'setuptools.command.test'.

For Poetry users, even locking in setuptools<72 does not [always] seem to work. For some installations it still seems to use setuptools>=72 from somewhere, and the PIP_CONSTRAINT environment variable does not seem to be obeyed by poetry. A workaround here is:

$ poetry export -o requirements.txt
$ poetry export -o constraints.txt -f constraints.txt
$ PIP_CONSTRAINT="$(pwd)/constraints.txt" poetry run pip install -r requirements.txt

In other words, export your locked requirements to traditional pip requirements.txt and constraints.txt files, then run pip in the Poetry environment to install dependencies. This way it properly appears to obey the PIP_CONSTRAINT environment variable.

You can run poetry install afterwards and it should come up with nothing to do, meaning it had exactly the same effect as poetry install.

For the poetry export commands, make sure you add the same arguments as you’d add to poetry install, e.g. --only main.

If pip gives you an error like:

ERROR: Can't verify hashes for these requirements because we don't have a way to hash version control repositories: ...

Then add --without-hashes to the export commands.

Solution/workaround is there : https://github.com/pypa/setuptools/issues/4519

If using docker and PIP or poetry, do the following :

RUN echo "setuptools<72" > constraints.txt
ENV PIP_CONSTRAINT=constraints.txt

(And you can then run your pip/poetry commands as normal)

If not, well, create a file constraints.txt at the root of your project with setuptools<72 as the file content
Then use export PIP_CONSTRAINT=constraints.txt to point to that file in the environnement variables.

Remove the fix once the upstream packages are updated

Please install setuptools < 72.0.0 as tmp solution -> run installation for you package/library.

Bit, I think, adding setuptools as a dependency to poetry will work unstable, since all packages are installed in parallel (even in batches) and in this case the build will be non-deterministic (depending on what is installed first, the setup tool or the library)

echo "setuptools<72" > constraints.txt
export PIP_CONSTRAINT=constraints.txt

poetry run pip install <affected_package>==<version>
poetry install

As a temporary workaround, try this:

pip install --upgrade pip-tools pip wheel
pip install setuptools==71.1.0

Run this before installing your packages.

The old version of setuptools has been depricated on 28th July 2024.
New version of setuptool==72.0.0 has bug.
For that you have to add 2 additional things:

• use setuptools<72.0.0
• use 1.0=0.40

WORKDIR /app
RUN pip install --upgrade pip
RUN pip install pipenv
RUN python -m pip install 'setuptools<72.0.0'
RUN python -m pip install 'wheel>=0.40,<1.0'
RUN pipenv install --system --dev
RUN pipenv install --system --deploy
EXPOSE 8000

CMD python manage.py runserver --noreload 0.0.0.0:8000