summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichał Górny <mgorny@gentoo.org>2022-06-17 07:13:45 +0200
committerStephen Finucane <stephenfinucane@hotmail.com>2022-06-17 14:28:04 +0200
commit90a7a127c2dbcaae63cff553792fd45666816b37 (patch)
tree269bf2fe32d7cdf6dde1a29079fcfcdb791aeb9f
parentb973f709e7a184c49f107a498a72f060eddd7375 (diff)
downloadwarlock-90a7a127c2dbcaae63cff553792fd45666816b37.tar.gz
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/
-rw-r--r--pyproject.toml4
1 files 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"