On 3 November 2015 at 16:02, Nathaniel Smith <n...@pobox.com> wrote: > On Nov 2, 2015 6:51 PM, "Robert Collins" <robe...@robertcollins.net> wrote: ... >> > Ugh. If 'pip (install/wheel) .' is supposed to become the standard way >> > to build things, then it should probably build in-place by default. >> > Working in a temp dir makes perfect sense for 'pip install >> > <requirement>' or 'pip install <url>', but if the user supplies an >> > actual named on-disk directory then presumably the user is expecting >> > this directory to be used, and to be able to take advantage of >> > incremental rebuilds etc., no? >> >> Thats what 'pip install -e .' does. 'setup.py develop' -> 'pip install -e >> .' > > I'm not talking about in place installs, I'm talking about e.g. building a > wheel and then tweaking one file and rebuilding -- traditionally build > systems go to some effort to keep track of intermediate artifacts and reuse > them across builds when possible, but if you always copy the source tree > into a temporary directory before building then there's not much the build > system can do.
Ah yes. So I don't think pip should do what it does. It a violation of the abstractions we all want to see within it. However its not me you need to convince ;). -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
