[Commented On] D11393: pep-517: remove the `build-backend` key to allow for users to build extensions

[gracinet (Georges Racinet)]

gracinet added a comment.


  I can confirm this makes  installation with pip include the Rust modules and set the module policy to `rust+c` with the following command lines:
  
    $pytthon -m pip install --no-use-pep517 --global-option --rust /path/to/mercurial/sources
    $pytthon -m pip install --no-use-pep517 -r requirements.txt
  
  In the latter case (which is crucial for Heptapod, the application I have in mind), the requirements file looks like this:
  
    /path/to/mercurial/sources --global-option --rust 
  
  it is not possible to specify this `--no-use-pep517` in the requirements file, because that is a global *pip* option (whereas `--global-option` is for global options of `setup.py`).
  
  I fully expect that `/path/to/mercurial/sources` can be replaced with the simpler `Mercurial==5.9.2` if this is released. In fact I also tried a `hg+https` requirement for the sake of it.

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D11393/new/

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

To: Alphare, #hg-reviewers
Cc: gracinet, marmoute, mercurial-patches
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-patches/attachments/20210922/7b150d28/attachment-0002.html>