Does pants have any mechanism for selecting resolve for specific dependency at call-time, CLI, or something local? Or "enforce" a specific resolve for a library from different binary targets? We use

torch

in multiple of our repos; and based on hardware and other specifications we need to switch which "flavor", which is done using localtags:

+rocm

or

+cuNNN

for GPU backends,

+cpu

for "CPU-only", or nothing. I've managed to get a bunch of different resolves to work, but I'm not sure how to tie this into dependency inference for local execution, nevermind trying to publish anything using this abomination of version management.

Can you just build a specific resolve of your binary target? I.e., add the resolve to the address:

path/to/some:target@resolve=RESOLVE

yep, parametrizing targets might be the way to go here: https://www.pantsbuild.org/docs/targets#parametrizing-targets

Awesome! And so if let's say

liba.foobar

imports

torch

, and I pass

@resolve=gpu

to

binary/main.py

does the resolve override recursively? I assume so as the opposite would be madness, just double-checking. Also; can I set a "default" parametrize?

Parametrized fields like

resolve

will be "passed down" correctly.