HI have a question (more of seeking opinion on something) is there any recommended convention one can use with

confetest.py

files. As am adopting pants from a monlith repo to a mon-repo. I wondered anyone either • copying the conftest.file into each root_pattern where its required ◦ this would cause heavy duplication, which might be ok if the conftest file stays consistent • having a shared folder that is also known by pants containing a conftest file and using symlink for the other packages to point to it. • does pants have some magic that makes that easier ◦ with the potential option of overriding or enhancing package specific conftets. sorry if this is open ended

Good question. It sounds like you're assuming that your repo should have many source roots, perhaps one per project?

could you elaborate on what you mean

With Pants, physical partitioning and logical partitioning can be decoupled. You can have one and only one source root that contains many logically separate projects and artifacts. It basically comes down to a choice with how people are comfortable working.

am trying with a structure like this

Understood. We just want you to understand that one option is to not structure like that. You won't lose your logical 3-part distinction, but it will make conftest sharing trivial.

where my thinking was that if I do that I get enough separation and also able to test and deploy it as separate lambda

That's where you're mistaken. You can have the logical separation and test and deploy seperately ~regardless of layout.

maybe am feeling very slow

Let me give you a concrete example. Just a sec.

am not settled on it, just wanted to explore things that will make it easier for me pants

Alternate physical layout , same logical partitioning:

src/
    addition/
    hello_world/
    math_utils/
    string_utils/
tests/
    ...

Test just libraries:

./pants test src/math_utils:: src/string_utils::

Package just hello_world lambda:

./pants package src/hello_world/::

ah I follow what you mean meaning you would potentially only have /src as a root_pattern. ...

Yeah. This is just one example. The layout is nearly arbitrary.

that definitely an option. will try it out. And play around some of the pants commands i would run for n+ package when running

./pants package ::

and would just need to add

python_awslambda(
    name="addition_function",
    runtime="python3.9",
    handler="lambda_function.py:lambda_handler",
)

to each "one that I want to package" in each

BUILD

file and get it working