I have a directory that has a (working)

python_distribution

(generating a setup.py) to which I want to add explicit constraints on the python version. This is in a monorepo with source roots defined as

src/*

. This config is working for the generated setup.py. However, I decided to instead use a pyproject.toml. But, when I add a pyproject.toml to the directory and set it as a resource for the distribution (like the example) pants starts complaining about the source root not being defined for the directory. How is adding the pyproject.toml file clobbering the global source root? And, how would I fix it?

Can you give a bit more info about your directory layout and where the

pyproject.toml

is in relation to it?

Roughly, it looks like this

.
├── BUILD
├── common
│   └── src
│       └── python
│           └── <package-name>
├── gear
│   └── <app-name>
│       └── src
│           ├── docker
│           └── python
├── distributed_package
│   ├── BUILD
│   ├── pyproject.toml
│   └── src
│       └── python
│           ├── BUILD
│           ├── __init__.py
│           ├── package_code.py
│           └── py.typed
├── pants.toml
└── requirements.txt

Ah, indeed,

pyproject.toml

is not in any source root. It probably shouldn't need to be, there might be some over-aggressive checks going on. But I think a workaround is to add the repo root as a fallback source root, as it is in that other example you linked to