From e2408ff516993f58df879818a8ff64c04ab5d0e9 Mon Sep 17 00:00:00 2001 From: Michael Adler Date: Wed, 4 Nov 2026 16:29:43 +0100 Subject: [PATCH] chore: switch to poetry-core backend Replace legacy `poetry.masonry.api` with `poetry.core.masonry.api`. The old backend lacks `build_editable()` (PEP 660 [1]), breaking editable installs with standards-compliant installers like uv or pip >= 21.3. For example, this allows developers to use uv instead of poetry for local development. poetry-core is Poetry's officially recommended build backend [2]. It is lighter (no resolver/CLI/plugins pulled in at build time) and supports the full PEP 517/660 interface. [1] https://peps.python.org/pep-0660/ [2] https://python-poetry.org/docs/basic-usage/ Signed-off-by: Michael Adler --- pyproject.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pyproject.toml b/pyproject.toml index 55ff2b4..ca8d843 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -42,5 +42,5 @@ flake8 = "^7.0.0" pytest = "^9.0.3" [build-system] -requires = ["poetry>=2.0.0"] -build-backend = "poetry.masonry.api" +requires = ["poetry-core>=2.0.0"] +build-backend = "poetry.core.masonry.api"