python.pkgs.google_cloud_storage requires setuptools at runtime.
This looks like a pattern used in other parts of the google bindings aswell, so we might want to fix those too

@flokli Whatever depends on google_cloud_storage that also needs setuptools will have this requirement satiated transitively because it's propagated here. So likely we won't notice it being an issue. Can we fix them all here?

hrm, it's not really inspectable.

@FRidh I wonder if we could add some script in fixup phase warning/failing on non-progated setuptools, but code like pkg_resources.declare_namespace(__name__) present.

But out of the scope for this PR.

I looked at the python google package dependencies of google_cloud_storage (only those, not all, as it's a lot), and added setuptools manually where used (it was needed everywhere).

We could create a hook that greps on pkg_resources and verifies if setuptools is in $out/nix-support/propagated-build-inputs. Then we could run a single job with this hook added to buildPython*.

@FRidh Thinking the same. Should be good and we could probably get them all in one go.

It's a pity there are so more many packages that use pkg_resources than I initially expected. At this point I am actually considering just adding setuptools again (on stable).

Next couple of days I'll be occupied with #71222. After that, could run a run with the proposed hook.