Support for multiple pyproject.toml files

[jossh-h]

We have a situation where we have multiple packages per repository, and the packaging system we use has its package definition file nested within the python namespace, ideally our PIP projects would follow the same structure eg:

  MyProject
 ┗ src
   ┗ libs
      ┣ foo
      ┃  ┣  main.py
      ┃  ┗ pyproject.toml
      ┗ bar
         ┣  main.py
         ┗ pyproject.toml

This hierarchy is not officially supported by setuptools or any other front/backends from what I can find,

If we use flit then we can have two separate *pyproject.toml files at the root:

  MyProject
 ┣ foo_pyproject.toml
 ┣ bar_pyproject.toml
 ┗ src
   ┗ libs
      ┣ foo
      ┃  ┗  main.py
      ┗ bar.py 
         ┗ main.py

Then build with the -f flag and pass in the input config file eg: flit -f foo_pyproject.toml build
This works but ideally we would use the same front/backend as our other package projects which is build/setuptools.

What are the chances of adding support for this? I am happy to work on this feature but wanted to gauge the feeling on adding this feature.

[uranusjr]

Doesn’t uv support your first tree with workspaces? (You need an additional pyproject.toml in the root.

[jossh-h]

Doesn’t uv support your first tree with workspaces? (You need an additional pyproject.toml in the root.

I couldn't get that tree working with uv and workspaces,

  MyProject
 ┗ src
   ┗ libs
      ┣ foo
      ┃  ┣  main.py
      ┃  ┗ pyproject.toml
      ┗ bar
         ┣  main.py
         ┗ pyproject.toml

One of the problems with the first tree is when setting the root of the namespace to ../../../src eg:

/MyProject/src/libs/foo/pyproject.toml

[project]
name = "foo-package"
...
...
[tool.setuptools.packages.find]
where =   ["../../../src"]
include = ["libs.foo"]

I get some odd behavior, for example building the wheel from the sdist via python -m build will error, but passing the --wheel and or --dist flag will build fine.

[layday]

pyproject.toml canonically marks the root of the project source tree. The flit flag is non-standard and most likely predates pyproject.toml. You might just have to bite the bullet and nest each package under its own project folder.