On Mon, Mar 18, 2013 at 4:48 PM, Lennart Regebro <rege...@gmail.com> wrote: > On Mon, Mar 18, 2013 at 3:13 PM, Marcus Smith <qwc...@gmail.com> wrote: >> 1) pip is *currently* very much a build tool in that it build/installs from >> source archives, but I understand the new model is for pip to eventually be >> working with pre-built wheels much of the time, with no build system >> required. > > I used the word "build tool" in the packaging summit, that was the wrong word. > My point is that is currently a tool to *install* distributions as > opposed to *create* distributions. I think it's best if it is kept > that way. I'd rather see the wheel command go into another tool used > to build distributions (and perhaps upload them to the cheeseshop).
No, that's not the intended use case of "pip wheel". It's intended for use as a multi-stage installation tool. Stage 1: install from sdist on a staging server which has development dependencies installed Stage 2: upload to a private PyPI index you control (perhaps just a directory published internally over HTTP) Stage 3: install from wheel on production servers without development dependencies For actual development use, it makes a lot more sense to install the wheel project and just use ./setup.py bdist_wheel. Cheers, Nick. > > [ I overheard the proposal to call such a tool "pup". ;-) ] > > //Lennart > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > http://mail.python.org/mailman/listinfo/distutils-sig -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig
