@aloof-angle-91616 I’m not sure this changes anything there? Fundamentally, there are two relevant files for a target:

target-specific subset of requirements.txt

(“unresolved deps I care about for this target”) and some kind of lockfile (“resolved transitive deps I will actually use for this target”) This proposal is just that we’ll store a third, non-target-specific file (“resolved superset of deps I may use”) of which target-specific lockfiles are guaranteed to be a subset? Basically just that we’re caching the result of a global resolve to constrain our future resolves, for consistency. Or am I mis-interpreting the proposal?