Add package to build from a dependency? #6796
Unanswered
rlaphoenix
asked this question in
Q&A
Replies: 1 comment 1 reply
-
|
What you are looking for is not how Python packaging works normally -- you need to build both packages and install them both (the namespaces will not conflict if you use implicit namespace paths -- if If you are interested in vendoring the third module in so that there is only one package, that feature is tracked at #4583. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a namespace named 'foo'. Under it there's two sub-packages. 'core' and 'commands'. When I run
poetry buildit works great and I end up with both sub-packages. However, I have a second project named 'foo-repository' added as a dependency. It's structure has the same named 'foo' namespace folder with two packages, 'core' (again) and 'services'.When I run
poetry buildI was expecting to have all three folders in the whl. Is this possible?I have poetry recognizing the namespace in
foo-repositorywith:Under poetry I can recognize the paths are different for these two namespaces. The 'core' and 'commands' when imported are in the main project git repository location. The 'services' and 2nd 'core' from 'foo-repository' are importing from the main project's venv.
Beta Was this translation helpful? Give feedback.
All reactions