[Distutils] GSoC 2017 - Working on pip
Justin Cappos
jcappos at nyu.edu
Fri Feb 10 17:04:57 EST 2017
I think the difference Sebastien is trying to say is that you need info
from *all* pieces of static metadata. Not just that from the packages you
will end up installing.
Backtracking dependency resolution will be much more like the wheel model.
If one does not backtrack (which is true most of the time), it only needs
the metadata from the things you end up install.
Justin
On Fri, Feb 10, 2017 at 4:36 PM, Donald Stufft <donald at stufft.io> wrote:
>
> On Feb 10, 2017, at 2:53 PM, Sebastien Awwad <sebastienawwad at gmail.com>
> wrote:
>
> If dependencies were knowable in static metadata, there would be a decent
> case for SAT solving. I'll try to get back to a write-up after the current
> rush on my main project subsides.
>
>
>
> The differences between backtracking and SAT solvers and such is perhaps a
> bit of of my depth, but just FWIW when installing from Wheel it’s basically
> just waiting on a new API to get this information in a static form.
> Installing from sdist still has the problem (and likely will forever) but I
> think it’s not *unreasonable* to say that using wheels is what you need to
> do to get fast dep solving and if people aren’t providing wheels it will be
> slow(er?).
>
> —
> Donald Stufft
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20170210/a7b5b1ab/attachment.html>
More information about the Distutils-SIG
mailing list