[bug#63139] [PATCH python 02/20] gnu: Add python-pyproject-hooks.

[John Kehayias via Guix-patches via <guix-patches@gnu.org>]

Hi Lars,

On Mon, May 01, 2023 at 08:58 AM, Lars-Dominik Braun wrote:

> Hi,
>
>> +               (replace 'build
>> +                 (lambda _
>> +                   (invoke "python" "-m" "build" "--wheel" "--no-isolation" ".")))
>> +               (replace 'install
>> +                 (lambda _
>> +                   (let ((whl (car (find-files "dist" "\\.whl$"))))
>> +                     (invoke "pip" "--no-cache-dir" "--no-input"
>> +                             "install" "--no-deps" "--prefix" #$output whl)))))))
>
> why is this necessary? As far as I see pyproject-hooks wants to be built
> using flit_core, which we have a fully bootstrapped version of. Same
> for pypa-build, which – as far as I can see – also builds using flit_core.
>

This gets to what I wasn't sure about, what exactly needs to be
bootstrapped and what depends on what. From what I remember and
thought, the newer python-pypa-build needs python-pyproject-hooks.
Which itself would be built with pyproject-build-system, creating a
circular dependency. But, I don't know anything about flit_core and
that system. So you are saying flit_core is used to build each of
these without a cycle then?

Can you layout what the new structure would be for updating
python-pypa-build with python-pyproject-hooks then? (And then
deprecate pep517.)

Thanks!
John