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
Originally posted by Wyko August 25, 2023
Hey all,
I'm working on two projects. Project B imports Project A as a dependency. On my local machine, I can specify the folder with Project A in it using poetry add -e. This lets me develop both projects concurrently.
How do I do that, while at the same time putting the correct repo path of Project A as well? That way anyone who does pip install on Project B gets Project A too.
The text was updated successfully, but these errors were encountered:
This is also related and has been discussed a lot. #1168
However, all these approaches "break" how poetry works on a very fundamental level. I would like to see a option for this as well. At the moment mpy workaround is to manually pip install my local dependency on top during dev.
Discussed in https://github.com/orgs/python-poetry/discussions/8366
Originally posted by Wyko August 25, 2023
Hey all,
I'm working on two projects. Project B imports Project A as a dependency. On my local machine, I can specify the folder with Project A in it using
poetry add -e
. This lets me develop both projects concurrently.How do I do that, while at the same time putting the correct repo path of Project A as well? That way anyone who does
pip install
on Project B gets Project A too.The text was updated successfully, but these errors were encountered: