Skip to content
Snippets Groups Projects
  • Raphaël Gomès's avatar
    58fe6d127a01
    pep-517: remove the `build-backend` key to allow for users to build extensions · 58fe6d127a01
    Raphaël Gomès authored
    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
    58fe6d127a01
    History
    pep-517: remove the `build-backend` key to allow for users to build extensions
    Raphaël Gomès authored
    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