Playing around with

v2.13.dev5

. Are there plans to let the

export

goal accept addresses to specific

python_requirements

targets? I saw in an example the use of

./pants export ::

but when trying to use a specific address it still resolves everything in

pants.toml

. Didn't see any documented args, so didn't try anything else to see if it's my own mistake (https://www.pantsbuild.org/v2.12/docs/reference-export)

Do you have a lockfile set up?

Yes, 3rdparty/BUILD has a python_requirements referring to a named resolve (python-default) with a requirements input file and lockfile in the subpath python. But I also have lockfiles declared for each tool used (isort, black, etc.) in pants.toml, and the export function always generates the venv for each tool, even when I pass as an argument the said python_requirements target address

3rdparty:3rdparty

One very minor issue-- when the command executes, it doesn't give any sort of status on what it's doing. Since it can take awhile to export everything, Pants appears frozen until it finishes.

Hmm yes I guess

export ::

will always export all the tool venvs? cc @hundreds-father-404

Yeah, I think we need something like

generate-lockfiles --resolve=<black>

. CLI specs like

::

don't map to tools

They could if we had the v1 thing where tools are defined by targets