You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When installing under docker (x86-64) I see ModuleNotFoundError: No module named 'setuptools.command.test' for version 0.4.0.
For now we are using one of the workarounds discussed at pypa/setuptools#4519 (PIP_CONSTRAINT env var pointed to a file containing setuptools<72.0). We have other dependencies that we need to do this for anyway so it's not blocking us but thought I'd give a heads up here.
The text was updated successfully, but these errors were encountered:
The problem is indeed caused by a change in setuptools 72.0.0. (As the error message will explicitly tell you, "This is an issue with the package mentioned above, not pip.".) Pip uses Setuptools by default to build projects that include a setup.py and don't explicitly ask for a different build backend in a pyproject.toml.
The removal of setuptools.command.test was reverted in 72.1.0 as an emergency measure, but all maintainers should expect it to be permanently removed soon.
The setuptools.command.test functionality was deprecated many years ago. Not to mention, it's intended purely for the developer's convenience - it's irrelevant to building the project (which also should be pre-built anyway as the project is pure Python).
Note that Setuptools is complete overkill for this wheel-building task for pure Python projects - but it does the job, and changing the build backend takes that little extra bit of work and understanding when the project was already using Setuptools before.
This project was unlucky enough to get attention on Stack Overflow for this issue.
pip 24.2 (or setuptools 72 that it brings in?) has removed a long deprecated feature that RandomWords is relying on at https://github.com/tomislater/RandomWords/blob/master/setup.py#L6.
When installing under docker (x86-64) I see
ModuleNotFoundError: No module named 'setuptools.command.test'
for version0.4.0
.For now we are using one of the workarounds discussed at pypa/setuptools#4519 (
PIP_CONSTRAINT
env var pointed to a file containingsetuptools<72.0
). We have other dependencies that we need to do this for anyway so it's not blocking us but thought I'd give a heads up here.The text was updated successfully, but these errors were encountered: