On 28 June 2018 at 09:55, Bernat Gabor email@example.com wrote:
I don't consider building from source a niche use case per se, given that pip is most widely adopted PEP-517/518 build frontend. What other build frontends there are or are to be recommended for usage (with setuptools/flint/poetry being mostly backends)?
The vast majority of uses of pip are `pip install xxx` which will typically download and install a wheel from PyPI. Those just work. Consumers of packages vastly outnumber producers. Use of pip to build packages for publication is an important use case, but (a) it's definitely not the most significant case and (b) it works pretty well. The biggest issues seem to be with use of pip in local development of applications and packages that will never be published on PyPI ("we use pip to install packages from our git repository, and our various tools have complex dependencies - how do we make a dependency on build-123 of package foo from git?") and yet those are far in the minority of actual use.
Basically it's the usual 80/20 rule - 80% of the problems come from 20% of the use cases - but exaggerated drastically (I suspect it's 99/1 or worse, in reality).
PS The biggest outlier here is the scientific stack, which has significant build challenges, and yet enabling them to robustly publish wheels is a critical use case.