# HG changeset patch
# User Raphaël Gomès <rgomes@octobus.net>
# Date 1631176948 -7200
# Node ID 58fe6d127a014d8dfc93a56b5e361944ee47a6c6
# Parent  1941064d37130f4683293dd6746def1f4f15c37f
pep-517: remove the `build-backend` key to allow for users to build extensions

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.

Differential Revision: https://phab.mercurial-scm.org/D11393

diff -r 1941064d3713 -r 58fe6d127a01 pyproject.toml
--- a/pyproject.toml	Fri Sep 17 21:04:21 2021 +0200
+++ b/pyproject.toml	Thu Sep 09 10:42:28 2021 +0200
@@ -1,6 +1,5 @@
 [build-system]
 requires = ["setuptools", "wheel"]
-build-backend = "setuptools.build_meta"
 
 [tool.black]
 line-length = 80