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

Pants

i have a scenario where we have a pyproject.toml, poetry project, which has mutiple packages in it
• src/package_1
• src/package_2
• src/package_2

```[tool.poetry]
name = "some_ubername"
...
packages = [
  {include = "package_1", from="src"},
  {include = "package_2", from="src"},
  {include = "package_3", from="src"},
]```
What I am attempting to do, is have three wheels, produced, package_1, 2 and 3
but I get into a trap that pants seems to think there are ambiguous owners.

is this "pattern" above used anywhere, or should I split to three different folders, or pyproject.toml's ?

I _do_ have two projects, one where it works.
and one where id doesn't and it's confusing me as to why.

is it possible to have two or more
`python_distributuon` entries, as siblings, where it is "clear" from sources includes, that
1. `python_distribution(1) --&gt; src/package_1`
2. `python_distribution(2) --&gt; src/package_2`
3. `python_distribution(3) --&gt; src/package_3`
It seems, that pants can't have them as siblings.