On 31 August 2017 at 17:50, Chris Barker <chris.bar...@noaa.gov> wrote: >> So I still expect pip wheel to be useful in a post-PEP 517 world. > > Maybe so -- but all pip should be doing is passing off the job to the > back-end.
It also handles locating the appropriate version on PyPI, downloading (including caching the downloads), building via sdist to avoid discrepancies caused by out of date intermediates (yes, the backend should be doing this, let's not open up the "trust the backend" argument again ;-)) Pip also handles *installing* the appropriate backends into the build environment. Certainly "pip install ." is mostly redundant compared to "flit build" (although again, pip provides a unified command line interface - you *could* read pyproject.toml in your deployment script, then install the backend and call the build_wheel hook, but why do that rather than using at least *some* frontend, if not pip? > Again, the package manager, well, manages the packages. It shouldn't be > concerned with how to build them. It isn't - it just manages organising the process of getting the build tools and running them. A simpler competitor to pip that *only* works with wheels and knows nothing about the build process is entirely possible under PEP 517. Indeed such a tool probably doesn't even need PEP 517. But there hasn't been enough demand for such a tool to be built yet, so I doubt people will suddenly be crying out for one when PEP 517 is implemented... Paul _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
