From 90a7a127c2dbcaae63cff553792fd45666816b37 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20G=C3=B3rny?= Date: Fri, 17 Jun 2022 07:13:45 +0200 Subject: Use poetry-core as the build backend Use poetry-core rather than poetry as the build backend. This is the recommended upstream solution, as it produces the same end result while not requiring the tools to install the complete set of poetry dependencies while building the wheel, effectively making the builds much faster. See "Why is this required?" at https://pypi.org/project/poetry-core/ --- pyproject.toml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pyproject.toml b/pyproject.toml index ed13e39..3118672 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -53,5 +53,5 @@ known_third_party = ["jsonpatch","jsonschema"] known_first_party=["warlock"] [build-system] -requires = ["poetry>=0.12"] -build-backend = "poetry.masonry.api" +requires = ["poetry-core"] +build-backend = "poetry.core.masonry.api" -- cgit v1.2.1