As an alternative to multiple resolves, we handled...
# general
As an alternative to multiple resolves, we handled a similar migration from many-poetries to pants by having one resolve, and only importing the 'main' pyproject.toml that had all the required dependencies (via path dependencies to each subproject, and/or copying their requirements) and have progressively moved to not use/remove the project pyproject.tomls at all (as we switched all required functionality into pants). We don't have pants load dependencies from each of the subproject's
: there is only one `poetry_requirements`/`python_requirements` target in our whole repo. This does force pants to be using everything the same versions of all dependencies across all projects, though.
🙌 1