Hi Pants! Is there a quick way to specify "all targets in and under this directory", like how we can

./pants test ::

at the top level?

./pants goal path/to::

does not seem to work.

What does pants say? Seems to work for me..

$ ./pants list tests::
tests/python/pants_test/init
tests/python/pants_test/init:tests
tests/python/pants_test/integration
tests/python/pants_test/integration:build_ignore_integration
tests/python/pants_test/integration:goal_rule_integration
tests/python/pants_test/integration:graph_integration
...

I want to use it in a dependency, like

dependencies=["path/to/module::", ]

and it said

InvalidTargetName: Address spec path/to/module:: has no name part.

Perhaps globs work in dependencies?

dependencies=["path/to/module/**"]

?

DM'ed

Ah yes,

./pants goal path/to::

works on the cmd line, but not in dependencies

thank you @happy-kitchen-89482! My use case was that I was trying to create a whl of a library

I'm not sure if our current macros would support this, but the upcoming "target generators" probably could

but if pex works i don't have to use a whl, hence i was also asking if i can load pex to the environmetn too

@hundreds-father-404 right?

pex is working, i was wondering if other than just running pex, we can also load pex into the environment, like how we load it to notebook

I'm not sure if our current macros would support this, but the upcoming "target generators" probably could

Yeah. You'll soon have two options: a macro https://www.pantsbuild.org/docs/macros which is really limited but sometimes all you need, or creating a "target generator" which can access the full Rules API. Meaning you can do things like run a process or read from the filesystem

so just this should work for now?

target(name="lib_name", dependencies=[<output of ./pants list path::>])

It does not include the subdirectory targets under path/to/module

Hm, you shouldn't need to explicitly depend on every target you want included due to transitive dependencies. For example, if you add

dependencies=["src/py/project:app"]

, and that itself already depends on

src/py/project/util

etc (e.g. via dependency inference), then you will pull in that dependency transitively Does

./pants dependencies --transitive path/to:python_distribution

already have some things you want, or it's missing everything?

that itself already depends on 

src/py/project/util

Pants thinks it doesn't depend on its submodules. the

__init__.py

files are empty, not explicitly importing submodules.

That implies your code uses a plugin system or other dynamic import mechanism? Otherwise dependency inference should generally follow all your imports and link those deps in.

Yeah, curious how this code is being used? It may be possible to tweak dep inference to do the right thing.

Thanks for the reply, all! Will take a deeper dive into this later