Hi all, Assuming that all the requirements are wheels and coming from PyPI. Installed using a recent pip.
How often do you think the resolution will be the same for all clients, and mostly be "pull everything from latest" ? If so, would it make sense to pre-compute thing on PyPI/warehouse at package publication time, and provide a resolution "hint" as an API endpoint ? If this "hint" is correct, it should avoid clientside work most of time. And the resolution can probably be efficiently updated as you only have to re-solve by looking as the dependees of previous version. -- M On Fri, Feb 10, 2017 at 1:36 PM, Donald Stufft <don...@stufft.io> wrote: > > On Feb 10, 2017, at 2:53 PM, Sebastien Awwad <sebastienaw...@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 > > > > > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > https://mail.python.org/mailman/listinfo/distutils-sig > _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig