poetry-multiproject-plugin
A Poetry plugin that makes it possible to use relative package includes.
Decision gist · record as of 2026-08-14
Yes, if you maintain a monorepo and need to share code across projects without duplicating it. The plugin fills a genuine gap in Poetry's design. However, the aging maintenance status (last release 377 days ago) means you should verify compatibility with your current Poetry version before relying on it for production builds. No known security vulnerabilities.AI-flagged interpretation of the facts on this page — verify before relying
Before you install
- Requires Poetry to be installed and a pyproject.toml file in the project root.
- The `--with-top-namespace` flag for library builds requires Python 3.9 or later.
- Low friction to install via `poetry self add`.
License · maintenance · safety
MIT (permissive) — MIT license is permissive; you can use this plugin freely in commercial and open-source projects with minimal restrictions.
last release 2025-08-02 (377 days) · last repo commit 2025-08-02 · 189 stars
0 known vulnerabilities (OSV.dev, 2026-08-14) · 84,520 downloads/mo, #13,991 on PyPI
Alternatives
Verify before relying
poetry self add poetry-multiproject-plugin
# Then in a project with relative includes in pyproject.toml:
poetry build-project
# Or check dependencies with mypy:
poetry check-project- Whether the plugin works reliably with Poetry versions released after the last plugin update (377 days ago).
- Performance impact when building large monorepos with many relative includes.
What it is and what it does
Poetry Multiproject Plugin extends Poetry with two new commands: `build-project` and `check-project`. The `build-project` command solves a core limitation of Poetry—it normally forbids package includes from outside the project root. This plugin copies the project and its relative includes into a temporary folder, rewrites the pyproject.toml, runs `poetry build`, and returns the built wheel and sdist. This enables monorepos to share code across multiple services or apps without duplicating it. The `check-project` command performs a similar workflow but runs `poetry install` and then `mypy` to validate that all dependencies are properly declared and the code type-checks correctly.
The plugin uses AST parsing to rewrite imports when building with a custom namespace (via `--with-top-namespace`), which is useful for libraries that need to avoid namespace collisions when multiple libraries from the same monorepo are installed together. It supports Python 3.8 through 3.13 and integrates directly into Poetry's command interface.
Use it for
- Build microservices in a monorepo that share utility packages without duplicating code across project folders.
- Validate that a project's dependencies are correctly declared by running mypy on the combined project and its relative includes.
- Organize Python projects according to the Polylith Architecture, where shared components live in a separate folder structure.
- Build multiple libraries from the same monorepo with different top namespaces to avoid import collisions when installed together.
- Set up a monorepo with a shared folder of namespaced packages that multiple apps can selectively include and build.
Worth the install?
AI-flagged interpretation of the facts on this page. Verify before relying on it.
Yes, if you maintain a monorepo and need to share code across projects without duplicating it.
The plugin fills a genuine gap in Poetry's design. However, the aging maintenance status (last release 377 days ago) means you should verify compatibility with your current Poetry version before relying on it for production builds. No known security vulnerabilities.
Install
poetry-multiproject-plugin on PyPI
Before you install
Low friction to install via `poetry self add`. The package is aging (last release 377 days ago) but the repository is active and not archived, with 189 stars. Depends on mypy, poetry, and tomlkit—all stable, widely-used libraries.
Requires Poetry to be installed and a pyproject.toml file in the project root. The `--with-top-namespace` flag for library builds requires Python 3.9 or later.
License in practice
MIT license is permissive; you can use this plugin freely in commercial and open-source projects with minimal restrictions.
Quickstart
poetry self add poetry-multiproject-plugin
# Then in a project with relative includes in pyproject.toml:
poetry build-project
# Or check dependencies with mypy:
poetry check-projectVerify before relying
- Whether the plugin works reliably with Poetry versions released after the last plugin update (377 days ago).
- Performance impact when building large monorepos with many relative includes.
Package facts
| License | MIT permissive |
| Python support | Supports the current Python release <4.0,>=3.8 |
| Install friction | Low. Pure-Python wheel |
| Runtime dependencies | 3 packagesmypypoetrytomlkit |
| Maintenance | Aging 377 days since the last release |
| Last repo commit | |
| First released | |
| Downloads | 84,520 / month, #13,991 on PyPI 30-day window, as of 2026-08-14 |
| Known vulnerabilities | None known OSV.dev, checked 2026-08-14 |
| Classifiers | License :: OSI Approved :: MIT LicenseProgramming Language :: Python :: 3Programming Language :: Python :: 3.10Programming Language :: Python :: 3.11Programming Language :: Python :: 3.12Programming Language :: Python :: 3.13Programming Language :: Python :: 3.8Programming Language :: Python :: 3.9 |
Evidence: poetry_multiproject_plugin-1.8.4-py3-none-any.whl
Tags
Let your AI agent find packages like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 14,416 PyPI packages by what they can do, searchable in plain language.
wish › “poetry monorepo plugin”
- poetry-multiproject-pluginA Poetry plugin that enables building and type-checking projects with…
- charmcraftlocalPacks Juju charms with local Python package dependencies by copying…
- poetry-dotenv-pluginA Poetry plugin that automatically loads environment variables from…
Give your agent the search over MCP, or paste the wish link into any chat.
More Build Tools packages
Provides reusable utilities for Python packaging interoperability, including version handling, specifiers, markers, requirements, tags, and metadata parsing according to standards like PEP 440 and PEP 425.
Wraps any iterable to display a real-time progress bar in the terminal or Jupyter notebook, showing iteration count, elapsed time, and estimated time remaining.
pip is the standard installer for Python packages, enabling you to download and install packages from the Python Package Index and other indexes into your Python environment.
Hatchling is a standards-compliant Python build backend that handles packaging, metadata, and distribution of Python projects when configured in a project's pyproject.toml file.
Generates Python gRPC service stubs and message classes from Protocol Buffer definitions, enabling developers to build gRPC clients and servers.
pre-commit is a framework for installing and running git hooks written in any language before commits are made, automating code quality and validation checks across multi-language projects.
Install it if your team needs consistent, automated validation at commit time.
See also poetry-core · charmcraftlocal · poetry-dynamic-versioning · mkdocs-multirepo-plugin · poethepoet · poetry · single-source · flake8-fixme · mkdocs-monorepo-plugin · poetry-dotenv-plugin