setuptools: [BUG] Many packages are no longer installable after test command is removed
For those landing on this issue, please see: (thank you @delfick for summarizing this)
- This functionality has been deprecated for 5 years, there is a separate issue for discussing if there would have been a better way of removing the functionality [FR] More gradual breakage of setuptools.command.test #4520
- For people using pip (or tools using pip, like poetry),
PIP_CONSTRAINTset to a file withsetuptools<72.0should work- For people using uv, there seems to be a bug where
UV_CONSTRAINTdoesn’t affect the version of setuptools used in build isolation (see ModuleNotFoundError: No module named ‘setuptools.command.test’ astral-sh/uv#5551) and in that case the solution is either--no-build-isolation(which should be considered a temporary solution) or getting packages to not use setuptools.command.test or using forks of those packages that comment out the use of setuptools.command.test (until setuptools releases a fix/revert)- To press subscribe to the ticket and/or thumbs up the top post instead of adding “same” comments
Quoted from https://github.com/pypa/setuptools/issues/4519#issuecomment-2255389347
setuptools version
setuptools==72.0.0
Python version
Python 3.9
OS
Linux
Additional environment information
No response
Description
The breakage change released on 72.0 breaks the default build isolation build of many packages since many of these packages do not pin on a particular setuptools version. There is also no way to pin to an older setuptools version as pip doesn’t offer a way to do this. Installing setuptools==71 first, then installing the package doesn’t work as the default build isolation resolves the dependencies without considering the lock file nor currently installed packages.
Based on these packages need to be patched with setup_requires before install, which is nearly impossible since we’d need to patch all packages.
Expected behavior
Install is successful.
How to Reproduce
- Create a virtual environment
- Upgrade to latest pip 24.2:
python -m pip install --upgrade pip pip3.9 install doubles==1.4.0
Output
me@my ~/repro-pip-fail
% pip3.9 install doubles==1.4.0
Looking in indexes: http://…
Collecting doubles==1.4.0
Using cached http://…/doubles-1.4.0.tar.gz (16 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... error
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> [17 lines of output]
Traceback (most recent call last):
File "/home/user/repro-pip-fail/venv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
main()
File "/home/user/repro-pip-fail/venv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
json_out['return_val'] = hook(**hook_input['kwargs'])
File "/home/user/repro-pip-fail/venv/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
return hook(config_settings)
File "/tmp/pip-build-env-h9ppcze_/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 327, in get_requires_for_build_wheel
return self._get_build_requires(config_settings, requirements=[])
File "/tmp/pip-build-env-h9ppcze_/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 297, in _get_build_requires
self.run_setup()
File "/tmp/pip-build-env-h9ppcze_/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 497, in run_setup
super().run_setup(setup_script=setup_script)
File "/tmp/pip-build-env-h9ppcze_/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 313, in run_setup
exec(code, locals())
File "<string>", line 2, in <module>
ModuleNotFoundError: No module named 'setuptools.command.test'
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 387
- Comments: 127 (10 by maintainers)
Links to this issue
Commits related to this issue
- introduce constraints.txt to workaround https://github.com/pypa/setuptools/issues/4519 — committed to netceteragroup/django-DefectDojo by pna-nca 2 years ago
- introduce constraints.txt to workaround https://github.com/pypa/setuptools/issues/4519 — committed to netceteragroup/django-DefectDojo by pna-nca 2 years ago
- Pin setuptools and use it See: https://github.com/astral-sh/uv/issues/5551 https://github.com/pypa/setuptools/issues/4519 — committed to fauust/buildbot by fauust 2 years ago
- Pin setuptools and use it See: https://github.com/astral-sh/uv/issues/5551 https://github.com/pypa/setuptools/issues/4519 — committed to fauust/buildbot by fauust 2 years ago
- Pin setuptools and use it See: https://github.com/astral-sh/uv/issues/5551 https://github.com/pypa/setuptools/issues/4519 — committed to fauust/buildbot by fauust 2 years ago
- introduce constraints.txt to workaround https://github.com/pypa/setuptools/issues/4519 — committed to netceteragroup/django-DefectDojo by pna-nca 2 years ago
- Workaround charm build failure to due the removal of `setuptools.command.test`. See issue: https://github.com/pypa/setuptools/issues/4519 — committed to canonical/charm-juju-backup-all by chanchiwai-ray 2 years ago
- Workaround charm build failure to due the removal of `setuptools.command.test`. See issue: https://github.com/pypa/setuptools/issues/4519 — committed to canonical/charm-cloudsupport by chanchiwai-ray 2 years ago
- ci: Workaround bug preventing Django test runs Workaround https://github.com/pypa/setuptools/issues/4519 by constraining `setuptools<72.0.0` when installing dependencies for Django tests. — committed to getsentry/sentry-python by szokeasaurusrex 2 years ago
- ci: Workaround bug preventing Django test runs Workaround https://github.com/pypa/setuptools/issues/4519 by constraining `setuptools<72.0.0` when installing dependencies for Django tests. — committed to getsentry/sentry-python by szokeasaurusrex 2 years ago
- remove TestCommand to fix compatibility with setuptools 72 Removed the import and the seemingly unused class PyTest. Looks like GH actions just use `exec pytest`. see https://github.com/pypa/setu... — committed to Shoobx/vcrpy by agroszer 2 years ago
- ci: Workaround bug preventing Django test runs Workaround https://github.com/pypa/setuptools/issues/4519 by constraining `setuptools<72.0.0` when installing dependencies for Django tests. — committed to getsentry/sentry-python by szokeasaurusrex 2 years ago
- ci: option --no-ansi added to ci steps to bypass https://github.com/pypa/setuptools/issues/4519 — committed to marcosschroh/dataclasses-avroschema by marcosschroh 2 years ago
- Workaround for breakage caused by setuptools v72 Based upon the suggestion here: https://github.com/pypa/setuptools/issues/4519#issuecomment-225544679 — committed to getredash/redash by justinclift 2 years ago
- temporary fix for vcrpy dependencies not being resolved see https://github.com/kevin1024/vcrpy/issues/855 and https://github.com/pypa/setuptools/issues/4519 Change-Id: If5f8fb87549ed8628a06b08a3a9c0... — committed to Checkmk/checkmk by deleted user 2 years ago
- temporary `pip install` fix as per https://github.com/pypa/setuptools/issues/4519#issuecomment-2255446798 — committed to datafold/demo by diveart 2 years ago
- Pin setuptools and use it See: https://github.com/astral-sh/uv/issues/5551 https://github.com/pypa/setuptools/issues/4519 — committed to MariaDB/buildbot by fauust 2 years ago
- Update to mobly-1.12.3 to avoid pip build errors Mobly < 1.12.3 was using `setuptools.command.test` in setup.py which breaks installs of the most recent setuptools release. See https://github.com/py... — committed to ksperling-apple/connectedhomeip by ksperling-apple 2 years ago
- ci: Workaround bug preventing Django test runs Workaround https://github.com/pypa/setuptools/issues/4519 by constraining `setuptools<72.0.0` when installing dependencies for Django tests. — committed to getsentry/sentry-python by szokeasaurusrex 2 years ago
Thanks for the report. I’ve yanked the 72.0.0 release while I investigate and determine if there’s a less invasive way to remove the command.
Given the lack of noise or reports since the release of 72.1.0, I believe the fix addressed the vast majority of use-cases affected by 72.0.0. My hope is that any remaining issues are isolated and readily addressable, but feel free to follow up here or in a new issue.
I want to thank everybody who was impacted by this for remaining civil, for your efforts in finding and documenting workarounds, and for providing constructive feedback on a change that was unnecessarily hostile to the ecosystem.
Yank, Yank, Yank!!!
Here’s how to work around this breakage:
Option 1: Create a file called constraints.txt
Then set
PIP_CONSTRAINT=/path/to/constraints.txtOption 2: Use
--no-build-isolation(and make sure you have an old setuptools installed)Option 3: Ask the maintainers of each package that is broken like this to adapt to new setuptools and wait for them to make a release
In general, I find it unfortunate that build isolation intends to increase reproducibility, but the tools given to users make this really tricky in practice. I think ^ is pretty hard for most Python users I know to come up with (and lacks e.g. the ability to hash pin). Probably wrong place to rant though, setuptools maintainers probably feel the pain of this more than anyone else! 😃
Edit: if setuptools does decide to revert something here, I have a suggestion in https://github.com/pypa/setuptools/issues/4520 for how the underlying change could be rolled out more gradually
Next, let me acknowledge - I did expect this change to have some disruption, but not nearly as much as it had. Sorry for the disruption.
I was anticipating that impacted users would have had visibility to the deprecation warnings and most packages would long ago have migrated and that the handful that remained could be addressed promptly. It seems instead the deprecation warning wasn’t placed with enough visibility for those installing affected packages, so the message only served to reduce reliance on the command for running tests, but not necessarily removing the command entirely. This statement is not an excuse, just context.
Maybe unpopular opinion - don’t yank it! The test command has been deprecated for 5 years, which is more than enough time for people to update their packages. Clearly something drastic like this was necessary to force stragglers to make the change (else it wouldn’t be an issue).
If the packages you are using don’t resolve this in the near future, maybe consider not using unmaintained packages ¯_(ツ)_/¯
Yank
v72.0.0ASAP!Guys, advising “downgrade setuptools, downgrade pip” and putting minuses under revert proposals, it’s easy to do when you develop single project on your own pc in your own venv. When you have tens or hundreds of projects, that use dependencies of dependencies, the game becomes much more exciting. rebuild base images, rebuild depending images, rebuild libraries… Do you really understand the scope of work?
holding prod environments hostage is not the best way to go about making package maintainers do their job is my opinion on the matter
epic morning
after an hour of googling, looks like I found the right bug 😃 this is an issue when installing
dbt-core==1.8.4, which listsLogbook==1.5.3as a requirement.Latest Logbook (1.7.0) seems to have fixed this but dbt-core still points to the older broken module.
Would it be possible to mark this version as yanked in pypi and follow a more gradual approach with deprecation warnings on install as mentioned in https://github.com/pypa/setuptools/issues/4520 ?
Especially installs with poetry seem to have issues and currently I couldn’t find a solution to overcome it. Did anybody find a solution for following or similar combination?
EDIT: Found a solution thanks to help of @ilpianista and @Hannes0730 , see my post below: https://github.com/pypa/setuptools/issues/4519#issuecomment-2255390400
(Of course we want to upgrade, but we’re still using sqlalchemy==1.4.49 which requires a major upgrade to 2.0 to support PEP 517).
seems that this one is going out of the control, based on quick Github search. it would be really nice if somebody from the dev team would make a definite statement whether we should do “dirty patches” in our deployment scripts with some random workarounds OR we should wait for the resolution in the
setuptoolsitself. in our case, we have more than a dozen of projects with custom deployment scripts and complex inter-dependencies.currently closely watching for this issue/thread to decide on future steps
While I agree with this in generally, this issue explains the problem with this “deprecation” quite well? As in - it should’ve been at least “screaming” in the console each time the deprecated piece of code was utilised. That way consumers of packages with this deprecation could’ve reached out to maintainers, asking for upgrade or smth similar
This is a tricky one in that regard, however. Main problem is that a maintaner might’ve been using this command in a way that consumer wouldn’t know about - and might’ve never encountered - and this deprecation notice, when the command runs, wasn’t actually shown, because it’s never called by consumers.
please yank this, none of these workarounds should be necessary and some of them don’t even work - disabling build isolation results in build errors for me.
i understand the desire to remove something that’s obsolete but clearly this wasn’t the right moment or way to do it.
I’m releasing the hot fix, which restores a small amount of the previous code to limit the breakage to “running setup.py test” but doesn’t break building a package that is importing the command, adding a deprecation warning for that case. It’s releasing as v72.1.0. I’ll be keeping a close eye on this issue and the issue tracker in case that change doesn’t adequately limit the disruption.
Not to be rude, but every comment in this thread (including this one, regrettably) leads to a large number of notifications and a large amount of noise that drowns out anything useful.
At this point, we should probably wait for a maintainer to provide an update.
this is ridiculous, this package is one of the most core packages and it has over 12 years of runway. Im very surprised as this bug is obvious the moment a realisitic test build is perform.
Please yank this version.
Please YANK!!! We can implement five different workarounds for various use cases, but the solution shouldn´t be this one. YANK!!
Pls YANK it!! All my CI dead bcs of it
Crowdstrike round 2?
I got a similar error today.
tbh… yes the workarounds work, but defining packages (versioned) outside of your normal tools just to get them installed is just not a workable solution for any kind of production app.
we are also getting similar error.
I just wanted to deploy at Monday instead of Friday and thats what happened
Could it 72.0.0 marked as yanked before other essential tools will be working with this change? 🙏
Can we revert this PR https://github.com/pypa/setuptools/pull/4458 ? I tried everything and was still not able to get it to work. We are working with poetry.
i got a similiar error too
This function can never be removed because removing it renders old package versions non-installable. It’s already too late to warn past developers about deprecation.
Python packaging has a huge problem with semantic versioning. The official documentation, to this day), recommends to always depend on the latest version of setuptools regardless of major version (and setuptools is not the only build backend doing this). This means that changes to setuptools can unexpectedly break nearly any sdist package, in this case rendering them non-installable. The change to setuptools version 72.0.0 indicates that it is not compatible with old packages, but the old packages accept any version and don’t even specify a single version that is known to be compatible. The builder has no better option than to install 72.0.0 and hope.
The simple way to fix this would be to create a setuptools2 and keep setuptools as a compatible version for packages that use it. However, even if the documentation says to specify a compatible major version, developers may continue not doing it because it’s convenient to them at the time, leading to this problem again years later. Maybe setuptools2 can error out if it detects that it is being required without a major version specified to avoid having to create a setuptools3.
To keep the name setuptools, maybe setuptools could detect that it is being required without a major version and replace itself with an older version or compatibility wrapper. It’s probably good enough to require the version be set in pyproject.toml and assume anything without pyproject.toml build-backend should use the oldest compatibility mode.
It’d also be possible for the package builder to do this kind of thing if it detects an unconstrained build backend version, but every package builder would need to know about the compatible fallback versions of every package build backend and that sounds like a good way to create inconsistent behavior across builders.
Oh this sucks so much!
@chrisirhc we may wanna add a couple more dotpoints to the description of this issue
PIP_CONSTRAINTenvironment variable mentioned below constrains what versions the package manager uses for this purposeedit: the version has been yanked https://github.com/pypa/setuptools/issues/4519#issuecomment-2255940870
Thank you, this solved our issue (using Poetry 1.8.3, Python 3.11.4).
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'.Maybe having a daily pipeline that tries to install the top N packages (say top 250 or other reasonable value) in pypi using the develop branch would help catching widespread regressions like these?
Revert plz, this breaks lots of projects
@chrisirhc are you able to please add to the description of the ticket that
PIP_CONSTRAINTset to a file withsetuptools<72.0should workUV_CONSTRAINTdoesn’t affect the version of setuptools used in build isolation (see https://github.com/astral-sh/uv/issues/5551) and in that case the solution is either--no-build-isolation(which should be considered a temporary solution) or getting packages to not use setuptools.command.test or using forks of those packages that comment out the use of setuptools.command.test (until setuptools releases a fix/revert)😃
edit: I’ve since suggested a couple more dotpoints https://github.com/pypa/setuptools/issues/4519#issuecomment-2255690881
edit2: the version has been yanked https://github.com/pypa/setuptools/issues/4519#issuecomment-2255940870
The official version of setuptools is now 71.1.0 again. https://pypi.org/project/setuptools/#history 😅
Facing same error here.
@ziga7631 The problem release (
72.0.0) was yanked yesterday. So in theory things should be ok now regardless. Just make sure your system isn’t using72.0.0specifically.There’s also a newer
72.1.0release with a fix in it as well.@ilpianista @Hannes0730 Thanks for your help, following worked for me too in poetry:
(sqlalchemy==1.4.49 is the problematic package here not supporting PEP 517) The current workaround for poetry seems to be… not using poetry to install 👌 (Somehow
RUN pip install sqlalchemy==1.4.49wasn’t required but that might be due to still using python 3.10 🤔 )Any workarounds for
poetry?doesn’t seem to work for some reason.
PS: YANK it!
Coming here from https://github.com/AUTOMATIC1111/stable-diffusion-webui
Putting 👇 in requirements.txt fixed it for me.
The good news is I think this has exposed what is maybe not a bug, but an oversight at least on my part - that despite having versions pinned throughout our code base and pipelines, isolated build of packages were not subject to those constraints.
Here’s a repo demonstrating how you can work around this in your Github Actions.
https://github.com/simonwhitaker/setuptools-demo
Hi, is option 1 compatible with
poetry add <package-name>? or is that pip dependent? I tried option 2 but I think--no-build-isolationis not supported inpoetry (1.8.2).RUN poetry install --no-interaction --no-build-isolation --without dev --no-ansi -vvvI am currently running this on Dockerfile
This breaks ~10 packages in my dependency chain which just specify:
so they don’t pin their setuptools build dependency, which makes them pull the latest version on every build. And that build happens in the isolated build environments for each package, so I don’t even really directly affect that somehow.
Not a good start into the week.
Makes me wonder if you should generally pin your build environment, there shouldn’t be any harm since it does not conflict with anything else? Assuming that you use build isolation though.
Also unable to use poetry at the moment…
For poetry users, exporting
requirements.txtandpip installwith the constraint worked for me.I was also faced this issue with
cssbeautifierlibrary, and solved by installing with--no-build-isolationoption in my case.I am also blocked because of this error
https://github.com/IBM/python-sdk-core/issues/202
For me the fix for the issue seems to be to run
pip install --upgrade pip-tools pip wheelbefore running the command that runs into theModuleNotFoundError: No module named 'setuptools.command.test'error messageSame issue here +1
same here +1
This is the related PR: https://github.com/pypa/setuptools/pull/4458
Unfortunately this is what leaving something in a long-term state of deprecation leads to. It becomes de-prioritized.
If I have code that’s been deprecated for an extended period, I prefer to change the deprecation notice to a stronger one including a date when we’re ready to remove it, which prompts people to re-prioritize.
No need to be laying blame anywhere here though, rather look to recommendations to make the process smoother in future.
In terms of workarounds,
PIP_CONSTRAINTSalone didn’t work for us with poetry, We had to do the following in our pipelines:not sure how to write this down without offending anyone. pretty much similar behavior as with python core devs - “[4 letter word] you, you’ve been warned in time, not our fault”. some people just want to see the world burn
p.s. at the end we decided to use the dirty hack with
PIP_CONSTRAINTin our production environment until the dust settlesI am having this issue with the
autobahnpackage while installing with pip (https://github.com/crossbario/autobahn-python/issues/1644).Changing my local projects requirements was not enough - the new version of setuptools was still being used despite pinning setuptools<72 for the reasons mentioned here https://github.com/pypa/setuptools/issues/4519#issuecomment-2255690881
Since I’m using poetry to build pip
requirements.txtI was able to successfully generate and useconstraints.txtas mentioned above (https://github.com/pypa/setuptools/issues/4519#issuecomment-2255652133).Thanks for the help everyone! 😅
https://stackoverflow.com/a/78806669/26556668
It’d be great to know when this is solved so folks can upgrade again.
setuptoolswasn’t even an explicit dependency and now it is an explicit devdependency.Same issue here +1
Same here - please revert 😦
I disagree Juanlu (hola!) , many build systems are centralised , meaning customers (teams) can provide a pyproject , requirements.txt or similar, and the system takes care of the rest. This means individual python teams do not have the option to specify commands, setup environment variables or other custom changes. For example, in my current company, adding this hotfix would have involved adding quite some hacky code into a non python codebase, just to support a temporary fix.
I also had problems with this. In my case I need to install the packages in a github action and in docker with poetry. It’s a DBT project, so as mentioned in https://github.com/pypa/setuptools/issues/4519#issuecomment-2254942140 it’s because of
logbook. So here is how I fixed it1. Constraints
Create the
constraints.txtwith justsetuptools<722. Docker
3. Github action
Hope it helps!
pipenv
Pipfile
pipenv lock
Dockerfile
Same issue.
See https://github.com/pypa/setuptools/issues/4520#issuecomment-2256130396. There are some tests, but they’re not as deep as you might hope. Probably that test could be expanded to the top 100 or top 250.
Yeah. Exact same issue.
dbt-core==1.8.3also pointed to Logbook==1.5.3. I tried to install Logbook==1.7.0 seperately but had conflict issue. It is failing only my C1/CD and I believed dbt needed to fix it asap.@jaraco can you please roll back the latest version? As it impacting many packages. After that, we can do the deprecate solution to ensure old packages still supported.
We’re working across 50+ repo’s so this isn’t an ideal solution, but will give it a go. @justinclift
same here +1, with Nylas sdk
Same issue with me.
With this work for me with Docker, python 3.12
requirements approach works, but we run poetry everywhere, would be nice to have a workaround for that too.
Was that command deprecated first at some point? Or was it removed right away? Feels like the release should mark it as deprecated first instead of ripping it out…
pip install -I --force-reinstall setuptools==71.0.0works for me
No, IIRC only explicitly running
python setup.py testwould give an error, but merely having asetup.pyreferencing the test command would not.Thanks @Jorden28, this worked for me.
my poetry generates bad links for some reason, so fast and ugly workaround for today is
seems that i should have also used
--no-build-isolationbut everything works well without itp.s. don’t yank) let’s finally update things
For Poetry/Docker users, I’ve managed to contain the fix to these three steps, though I did have to iterate to find all the dependencies that were broken
You can run that before your usual
RUN poetry installsteps, which won’t re-install those packageshttps://github.com/pypa/setuptools/issues/4519#issuecomment-2254983472 does not work for folks who use poetry.
For those using docker and poetry,
This is how my dockerfile looks now, and it works for me
I was facing this problem when I wanted to install Django Channels with Daphne. I found this solution and used the following command:
pip3 install --no-build-isolation --no-cache-dir "setuptools<72"For
uvusers, this worked for me:This worked for us using poetry and docker. In the dockerfile:
+1
FOR POETRY I think this worked for me with PIP_CONSTRAINT combined.
In my case , I deupgrade my setuptools to version 71.1 solved the problem as well
That is not correct, workarounds existed before setuptools 72.0.0 got yanked, see https://github.com/pypa/setuptools/issues/4519#issuecomment-2254983472
@chrisirhc please update issue to link to https://github.com/pypa/setuptools/issues/4519#issuecomment-2255940870 and https://github.com/pypa/setuptools/issues/4519#issuecomment-2255961257
I suppose you could do
poetry run pip install "setuptools<72"thenpoetry run pip install --no-build-isolation <your package>- the constraints.txt file is only a static way of doing itWe are also using poetry, but did anyone solved it without creating a constraints.txt file?
for those using poetry, this helped solve the issue (thanks to many comments above)
but still dunno how to fix this in a cleaner way 🤨
Did someone figure out how to fix this on Pants package builds?
Works for us as well to fix the dbt package issue 👍
For some reason, this seems to work fine now with us:
python -m pip install --force-reinstall setuptools==71.1.0 && python -m pip install --no-cache-dir --no-build-isolation dbt-snowflake==1.7.2I don’t know man
thanks @omerbe-nym worked for us
This workaround seems to be working, install the problematic package via pip(with constraints) and the rest via poetry
FYI for people using pip-tools that wants a workaround, make sure you both install setuptools version 71.1.0 and use pip-sync and pip-compile with the
--pip-args --no-build-isolationflag@Artui have a look to https://github.com/pypa/setuptools/issues/4519#issuecomment-2255263220
Issue for us as well. Persists even though setuptools are pinned to 71.1.0.
Good morning, everyone! Yup, ran into a similar problem when our GH workflows started crashing after setuptools dropped this major update. For me, it’s breaking down while installing SQLAlchemy (any solution apart from restricting setuptools to bump up to 72? Why they removed test without any sort of indication):
@Luke31 after several attempts, it looks like this one worked: