get the build passing

[chris48s]

Explanation:
Builds started failing running pip check with

Rtree 1.2.0 is not supported on this platform

If I pip install pip==24.1, pip check tells me everything is fine

If I pip install pip==24.2, pip check tells me Rtree 1.2.0 is not supported on this platform

For the moment I suggest we pin pip to get things moving again, but I'll try and see if I can find out exactly what the issue is. To me this looks like a false failure though.

[chris48s]

I reckon this might be pypa/pip#12884

[chris48s]

OK, so turns out this is actually fixed in rtree==1.3.0
New solution: upgrade rtree, leave pip as it was.

[chris48s]

I re-generated the requirements files using:

pip-compile --allow-unsafe --generate-hashes --output-file=requirements/constraints.txt --strip-extras requirements/constraints.in --upgrade-package rtree

to re-lock requirements/constraints.txt

and then

pip-compile --allow-unsafe --generate-hashes --output-file=requirements/base.txt --strip-extras requirements/base-constrained.in --upgrade-package rtree

to re-lock requirements/base.txt

That seemed right 🤞

I'm not sure why pip-tools took setuptools out of the lockfile here. Tbh, your pip-tools setup on this repo is pretty fiendish and also a bit under-specified. I think I'm going to need a bit of a primer on this before I can really do substantial work on the dependency tree on this repo. From memory, I feel like whether to include setuptools in lock files is something pip-tools went back on forth on a bit in different releases. There is no specific pip-tools version specified in the requirements or docs. I locked this using pip-tools==7.4.1. Let me know if you want me to re-lock using a different pip-tools version. Also if I didn't use the right combination of commands..