check out https://www.pantsbuild.org/docs/project-introspection for some similar commands like how to filter to only get

python_tests

targets, for example

Cool, now it's showing some third party requirements, but I'm still not seeing the dependencies on the

lib

or

resource

targets. For example: https://github.com/mitodl/ol-data-pipelines/blob/putting_on_pants/src/ol_data_pipelines/edx/solids.py#L25-L33

Based on that I would assume that the output should show modules from both of those targets, but this is what I'm seeing.

./pants dependencies --dependencies-type=source-and-3rdparty src/ol_data_pipelines/edx/                                                                                                                                                                                                                                                                                                       
//:dagster
//:httpx
src/ol_data_pipelines/edx/__init__.py
src/ol_data_pipelines/edx/api_client.py
src/ol_data_pipelines/edx/repositories.py
src/ol_data_pipelines/edx/schedule.py
src/ol_data_pipelines/edx/solids.py
dagster==0.9.14
httpx==0.16.1

All of those have python_library() targets which have the same files in the sources() field.

You can see which targets “own” a file by running

./pants list path/to/file.py

. Generally, you want it to be only 1 value

Ok, I've just updated the repo with your recommendations. For some reason though it's still not showing the

lib

and

resource

modules in the dependency list.

(I've pushed all of the changes to the branch in GitHub as well)

also, note that

resources

need to be depended on explicitly, because pants cannot infer their usage

so if the files owned by https://github.com/mitodl/ol-data-pipelines/blob/putting_on_pants/src/ol_data_pipelines/edx/BUILD need resources, you might need a dependencies list there

good luck 😃

Things still aren’t working correctly, still digging. But that fixes one of the problems

After making that fix I'm seeing the expected resolution (and after removing the explicit dependencies in the BUILD file)

So, for the case where I want the edx package to be a target that I package as an independently deployable unit, does that mean that it should have a BUILD definition in that directory, rather than just having the one definition at the root of src?

Pardon the delay with this one. So, the

python_library

is sort of a misnomer. It doesn’t imply any thing about how you deploy your code, it’s nothing more than a way to set metadata on some Python source code. A more apt name would be

python_srcs

, for example. The reason to use more granular vs. coarser

python_library

targets is how fine-grained you want your metadata to be. For example, you might want to only set one file to have overridden Python interpreter constraints, vs. an entire subtree. We generally recommend 1 BUILD file per directory because it tends to be the simplest heuristic and scales well whenever you do need to add metadata For your deployables, you explicitly say which dependencies you want in it, then those and all their transitive deps will be pulled in. You can either depend on a whole

python_library

target, which is shorthand for depending on all its files in the

sources

field, or you can pick out certain files from it using “file addresses” to be more fine-grained. https://www.pantsbuild.org/docs/targets#dependencies-and-dependency-inference

My next question is in how to add package metadata that gets propagated to setup.py, etc. such as things like trove classifiers, authors, etc.