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

Pants

Another win for us: migrating python tests and enabled `[python-infer].assets`.
• Run test
• test fails "No such resource: XYZ"
• Add relevant `BUILD.pants`
• test succeeds
No need to declare the `overrides: {"filename.py": dependencies: ["resourcepath1", "resourcepath2"]}`
:smiling_imp:

Where can I read up on the path inference? We often do things like `pathlib.Path(__file__)` and potentially some form of `.parent` or `.parents` and get the necessary resource/file.

There's not much documentation on semantics, but <https://www.pantsbuild.org/v2.11/docs/reference-python-infer#section-assets>

As you can hopefully imagine it's quite simple today.
Basically it takes strings with some number of slashes in it (configurable) and tries to match them to `resources` relative tot he files' parent or `files` relative to build root.

So `pkgutil.get_data("data/foo.txt")` would be inferred if there's a resource at `__file__ / ".." / "data" / "foo.txt"`

I'm excited also that we can continue to improve this inference over time. Josh laid the foundation