Poetry Core
A PEP 517 build backend implementation developed for Poetry. This project is intended to be a lightweight, fully compliant, self-contained package allowing PEP 517-compatible build frontends to build Poetry-managed projects.
Usage
In most cases, the usage of this package is transparent to the end-user as it is either used by Poetry itself
or a PEP 517 frontend (eg: pip).
In order to enable the use of poetry-core as your build backend, the following snippet must be present in your
project's pyproject.toml file.
[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"
Once this is present, a PEP 517 frontend like pip can build and install your project from source without the need
for Poetry or any of its dependencies (besides poetry-core).
# install to current environment
pip install /path/to/poetry/managed/project
# build a wheel package
pip wheel /path/to/poetry/managed/project
Why is this required?
Prior to the release of version 1.1.0, Poetry was a project management tool that included a PEP 517
build backend. This was inefficient and time consuming when a PEP 517 build was required. For example,
both pip and tox (with isolated builds) would install Poetry and all dependencies it required. Most of these
dependencies are not required when the objective is to simply build either a source or binary distribution of your
project.
In order to improve the above situation, poetry-core was created. Shared functionality pertaining to PEP 517 build
backends, including reading pyproject.toml and building wheel/sdist, were implemented in this package. This
makes PEP 517 builds extremely fast for Poetry-managed packages.
Contributing
Contributing is similar to the main poetry repo:
# For example:
poetry install
poetry run pytest
For full documentation, see the full contributing documentation.
Release files for poetry-core 2.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| poetry_core-2.5.0.tar.gz | 455.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| poetry_core-2.5.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 869.3 kB
Release files / poetry_core-2.5.0.tar.gz
| Download URL | poetry_core-2.5.0.tar.gz |
|---|---|
| Size | 455.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
81d04c9253b19d0604718268d781867c8f7b2128e5b25bbf1e84141eec6b89c4
|
|
BLAKE2b-256 checksum How to use checksums |
42b550f1fda26c4fe5b1d6ce5cdf0391bdfa1ca12fdcb8ad68344d5cf678fc90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.
Transparency logRelease files / poetry_core-2.5.0-py3-none-any.whl
| Download URL | poetry_core-2.5.0-py3-none-any.whl |
|---|---|
| Size | 413.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
98ee465b66f7e14bb9fbe68fb5e00d0cff184f036993ec94610ae4b5612f3add
|
|
BLAKE2b-256 checksum How to use checksums |
b7257ed0a2ea4fe12f7fd0394387b5debbcd6fdbd06e5ac9daab96ba11471da8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 19, 2026.
Transparency log
