Skip to content

Commit

Permalink
Use poetry-core as the build backend
Browse files Browse the repository at this point in the history
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/
  • Loading branch information
mgorny authored and stephenfin committed Jun 17, 2022
1 parent b973f70 commit 90a7a12
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -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"

0 comments on commit 90a7a12

Please sign in to comment.