Setuptools has finally removed the test command in v72, after 5 years of the depreciation warning.
Now it seems lots of modules are failing because they never did change their test suite.
Through the github issue for setuptools I've now discovered PIP_CONSTRAINT
https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-c
https://github.com/pypa/setuptools/issues/4519#issuecomment-2254983472
@markwalker constraint is great! Very useful to not duplicate prod requirements into dev.
@markwalker dateutil
got hit by this, but to be fair, the only reason we are failing is that we’re importing TestCommand
for the explicit purpose of failing the test suite if you execute setup.py test
.
@markwalker they only had 5 years time to do so.
@melroy yeah this is a good way to find unmaintained packages.
@markwalker Aaaaand it's yanked
@astrojuanlu ah yes. I didn't think they'd do that.
@markwalker Yeah, surprising. But Jason is a kind soul and the impact was really noticeable.
I guess now dozens of projects got the memo that this won't be around forever, hopefully they will migrate? But it doesn't fix old projects.
Maybe `pip` should just assume an old version of setuptools if no `pyproject.toml` was found. Otherwise this is an impossible problem to solve. cc @pradyunsg
@markwalker A memorable event