Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

the default `sources` argument if none is given is inferred to be `sources=['*.py']` (just the current directory) for `python_library()` targets

```python_library(
    sources=['**/*.py'],
    dependencies = [

    ]
)```

filedeps goal still gives the "common" not found in "ns/bar/common"

sorry, that's expected. could you try `./pants filedeps ns/bar`?

oh, duh, but now `filedeps ns/bar` is much more verbose, yes

in `ns/foo/tests/BUILD` you would need to have:
```python_tests(
  dependencies=[
    'ns/bar',
  ],
)```
i assume you have figured that out though

```python_library(
        dependencies = [
        "//:pytz",
        "//:python-dateutil",
        "//:requests",
        "//::PyYAML",
        "ns/core",
        "ns/config",
        "ns/bar",
    ]
)```

I added them as they came up in complaints during `pants test ns/foo/tests`

and now, I do indeed get past the original bug

`ResolveError: Directory ":" does not contain any BUILD files.`

not a problem, i'll be here until you've gotten past the build issues

we could also improve that error message, `//::` is never going to be a valid address, i'll make an issue

seems like in the BUILD file at the top of the pkg, one needs `sources=['**/*.py'],`

what is the rule on how far down the tree BUILD files are required?

you do not need to place any further BUILD files if you use the `**/*.py` recursive globs as above

seems one does need them at the top of pkg/tests/  if one uses such pkg/tests subdirectories?