On Sun, Nov 12, 2017, at 07:21 PM, Paul Moore wrote:
> Is it (in your opinion) something that pip might be able to use? The
> biggest potential hurdle, I would imagine, is that if pep517.envbuild
> uses pip to install dependencies, and pip uses pep517.envbuild,
> there's a risk of a recursive loop that could result in starting an
> arbitrarily large number of processes on the user's machine (this is
> one of the issues that has stalled the current work on PEP 517 for
> pip). On the other hand, other frontends depending on pip (indirectly,
> via pep517.envbuild) might seem a bit odd.
I would guess that pip could use the lower-level interface directly, but
it might want to control how dependencies are found and installed. The
higher level part is based on code already in pip
(pip._internal.wheel.BuildEnvironment), so hopefully integrating it
shouldn't be too much work.
I've also just added another module to test the hooks for a project and
point out any problems. It's used like this:
python3 -m pep517.check path/to/source
Thomas
_______________________________________________
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
