Patchwork D11393: pep-517: remove the `build-backend` key to allow for users to build extensions

login
register
mail settings
Submitter phabricator
Date Sept. 9, 2021, 9:13 a.m.
Message ID <differential-rev-PHID-DREV-bwh6rgmjr5hy4c65vrby-req@mercurial-scm.org>
Download mbox | patch
Permalink /patch/49709/
State New
Headers show

Comments

phabricator - Sept. 9, 2021, 9:13 a.m.
Alphare created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.

REVISION SUMMARY
  PEP 517 changed how projects should define their build dependencies.
  The presence of a `pyproject.toml` file changes the behavior of `pip` to
  conform to PEP 517.
  Since we haven't updated the `setup.py` file yet (I'm not even sure we're not
  an edge case which would make it harder/impossible, I have not tried yet), this
  is a workaround to issue6589: it allows users to pass `--no-use-pep517` to pip
  to revert to the legacy installer. The build backend is simply assumed to be
  the `build_meta:__legacy__` one.

REPOSITORY
  rHG Mercurial

BRANCH
  stable

REVISION DETAIL
  https://phab.mercurial-scm.org/D11393

AFFECTED FILES
  pyproject.toml

CHANGE DETAILS




To: Alphare, #hg-reviewers
Cc: mercurial-patches, mercurial-devel

Patch

diff --git a/pyproject.toml b/pyproject.toml
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,6 +1,5 @@ 
 [build-system]
 requires = ["setuptools", "wheel"]
-build-backend = "setuptools.build_meta"
 
 [tool.black]
 line-length = 80