You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm looking to use pants in a monorepo that builds two Python distributions:
library1 0.1.0
library2 0.1.0
Where library1 is a dependency of library2. If I define library1 in library2's pyproject then the Poetry virtual environment installs it successfully, but the build package doesn't reference the correct version. If I define the version as 0.1.0 then the package is correct but the Poetry virtual environment doesn't find the package.
Is there a pattern for doing this? For example, should I have an intermediate step of building the packages using pants package and then adding dist as a Python repo somewhere? Something with the PYTHONPATH?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello all,
I'm looking to use pants in a monorepo that builds two Python distributions:
library1 0.1.0
library2 0.1.0
Where library1 is a dependency of library2. If I define library1 in library2's pyproject then the Poetry virtual environment installs it successfully, but the build package doesn't reference the correct version. If I define the version as 0.1.0 then the package is correct but the Poetry virtual environment doesn't find the package.
Is there a pattern for doing this? For example, should I have an intermediate step of building the packages using pants package and then adding dist as a Python repo somewhere? Something with the PYTHONPATH?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions