Hi all 👋 , I'm a bit surprised about an aspect of pants tool lockfiles / resolves, and was hoping to get some clarity on this point: Is there a reason for the pytest subsystem's requirements option, or the mypy subsystem's requirements option when both of those already specify their requirements via the resolve lockfiles? I would have assumed the lockfile is the requirements for these tools, so it feels a bit like duplicative config code, but maybe there's a detail I'm missing on why these subsystem options are necessary?

The requirements option is for the sunset of the lockfile that the tool needs to run. If you already have those requirements locked (for example by having one big default python lockfile) you need only list the target address there, not a foo==1.2.3 requirements string.

I'm guessing you meant subset 😅? So it's more a feature to support a single monolithic lockfile / resolve, or some potential for combining various tools into a single lockfile, but not as much for separate per-tool resolves like pants ships with?

correct - you can point to some larger lockfile, but only depend on a subset of it. This is useful e.g., when you depend on pytest both as a tool and as a library (for your in-repo pytest customizations for example) and you want to use the same lockfile for both