I fail on understanding how to configure the

python_distribution

in the BUILD file when building wheels. I would like to use a

pyproject.toml

file as the source of metadata, that also defines the python source files. If I understand the flow correctly, the

pants package

command do the building in a sandbox and therefore need to know about the paths to use. I got the

pyproject.toml

right, and the Python files too, if I specify one of the targets. Is it possible to specify the top folder only? Current setup, in a BUILD file at a subfolder (projects/my_fastapi_project/BUILD):

resource(name="pyproject", source="pyproject.toml")

python_distribution(
    name="my-fastapi-project",
    dependencies=[
        ":pyproject",
        "bases/example/greet_api:greet_api",
    ],
    provides=python_artifact(),
    sdist = False,
    generate_setup = False,
)

I would like to be able to set the "bases" part as something like

bases

or

bases/*

or even

bases/example

- but that causes failure in the package command. Posting my experimenting-repo in a thread (with the commits showing the steps I'm taking to learn Pants.

if

bases/example/greet_api:greet_api

is the entry point, and it transitively imports everything it depends on, then dependency inference should pull in all the deps you need. Pants will plop those into a sandbox, along with pyproject.toml, and then run setup.py (or an alternative pep517 build backend of your choice). So if the wrong thing is happening the first place to investigate is the sandbox.

Thanks! The behavior is correct, I didn’t understand how Pants knew about the components, but understand now that it follows the imports.

Yeah, this is useful to browse: https://www.pantsbuild.org/2.20/reference/subsystems/python-infer