How do I specify multiple subdirectories as a dependency of a

python_distribution

? Do I need to list all of them individually? Or is there some way to say “All

python_source()

targets which are in subdirectories of this

BUILD

file”?

I had to capture all my sources in one top level

python_sources

target and then add that target to my dependencies for my distribution.

I had to capture all my sources in one top level

python_sources

target

How did you do that?

Moved it to the top level and then changed the

sources

glob pattern to

**/*.py

Ah

And then deleted all the

BUILD

files below that

Did

./pants tailor --check

have a problem with that?

Nope, tailor just looks for sources that don't have a resolvable target

Woop! Thanks for the help 😄

Thanks for the help @high-yak-85899 🙂 @future-oxygen-10553, in case you haven't yet seen it, it's often particularly a good idea to use

overrides

when you're using recursive sources globs like that. It keeps metadata as precise as possible

python_tests(
   sources=["**/*_test.py"],
   overrides={
      "subdir/foo_test.py": {"timeout": 120},
  },
)

(You can use globs in the key, like with

*

. And you can use a tuple for the key for multiple globs / file names

Thanks @hundreds-father-404 I have used overrides for skipping linting on files before, so I’ve seen that pattern 👍

more generally, because of dependency inference, you should only really need to mark the “root” modules that are part of the distribution

@witty-crayon-22786 What do you mean by “root” modules? If I have something like:

package-name
|--- __init__.py
|--- submodule/__init__.py
|--- submodule/sububmodule/__init__.py
|--- BUILD
BUILD
pyproject.toml

for a library, if you’re exposing a particular public API out of some modules, then those modules would be “roots”… anything that those modules depend on needn’t be listed

I see

(although the plugin list i linked above might look large, it’s still only the “roots”… the transitive dependencies of the plugins are ~500 modules)

Thanks!

having said that, this is still a manually maintained list. that means that if something is not intended to be part of your public API, you could skip putting it in there… but you could also forget to put it in there.

Thanks, Stu. Great points to remember when we start making new distributions. In my case, I had a whole bunch of independent roots that would have to have been manually included, but I can see how a more traditional distribution is easier to list out.

…cross referencing https://pantsbuild.slack.com/archives/C046T6T9U/p1662671864877109, which raised this again recently.