There's two ways to do this: 1. use resolves to have separate requirements files, and set the appropriate resolve per target: https://www.pantsbuild.org/docs/python-third-party-dependencies#warning-multiple-versions-of-the-same-dependency (potentially using `__defaults__`s to set it for a whole subtree) 2. only import one set of requirements and use it for the whole repo, e.g. add a parent requirement file that just has lines like

-r path/to/requirements.txt

,

-r another/path/requirements.txt

, and only one

python_requirements(...)

target in the whole tree The second one is likely to be simpler/smoother (having a single set of dependencies for the majority of the repo).