Support subprojects in a poetry project

### Background & Rationale This request is inspired by [RPM Package Manger](https://rpm.org/)’s capability to build [subpackages](http://ftp.rpm.org/max-rpm/s1-rpm-subpack-spec-file-changes.html) from the same [Spec File](http://ftp.rpm.org/max-rpm/s1-rpm-build-creating-spec-file.html). Here, I want to propose and discuss replication a version of this capability can be replicated within poetry to allow for simplified user experience for a python project maintainer, especially when either maintaining namespace packages and/or multi-project source trees. While strict project separation is a good thing in most cases, it might not always be the more pragmatic scenario for package maintainers. For our purposes here, we can refer to each of theses packages as a subproject. And all subprojects are managed under a single poetry project. This means that there is only a single `pyproject.toml` file and a shared project root directory with either a shared source tree or independent source trees (subdirectory) for each subproject. ### Description Let us consider the scenario of multiple namespace packages being maintained in a single repository with the following structure. ```console namespace-project/ └── src └── namespace └── package ├── one │ └── __init__.py ├── three │ └── __init__.py └── two └── __init__.py ``` Note that this will still apply even

Posted by abn on Apr 5, 2020, 7:44 PM

Tags

• support (Other)

Related issues

• some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
• I think of this as the kiosk economy.
• What a goofy comment.
• There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
• Compose support in WSLc
• [RFC] Roadmap to v2.0