On Thu, Nov 5, 2015 at 11:29 PM, Donald Stufft
I’m not at my computer, but does ``pip install —no-clean —build <insert build dir>`` make this work?
No, that option seems to not work at all. I tried with both a relative and an absolute path to --build. In the specified dir there are subdirs created (src.linux-i686-2.7/<pkgname>), but they're empty. The actual build still happens in a tempdir. Ralf P.S. adding flags for the various issues (/ things under discussion) this is what I actually had to try: pip install . --no-clean --build build/ -v --upgrade --no-deps :(
On Tue, Nov 3, 2015 at 6:10 PM, Chris Barker - NOAA Federal < chris.barker@noaa.gov> wrote:
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
into a temporary directory before building then there's not much the build system can do.
This strikes me as an optimization -- is it an important one?
Yes, I think it is. At least if we want to move people towards `pip install .` instead of `python setup.py`.
If I'm doing a lot of tweaking and re-running, I'm usually in develop mode.
Everyone has a slightly different workflow. What if you install into a bunch of different venvs between tweaks? The non-caching for a package
On November 5, 2015 at 5:25:16 PM, Ralf Gommers (ralf.gommers@gmail.com) wrote: tree like
scipy pushes rebuild time from <30 sec to ~10 min.
I can see that when you build a wheel, you may build it, test it, discover an wheel-specific error, and then need to repeat the cycle -- but is that a major use-case?
That being said, I have been pretty frustrated debugging conda-build scripts -- there is a lot of overhead setting up the build environment each time you do a build...
But with wheel building there is much less overhead, and far fewer complications requiring the edit-build cycle.
And couldn't make-style this-has-already-been-done checking happen with a copy anyway?
The whole point of the copy is that it's a clean environment. Pip currently creates tempdirs and removes them when it's done building. So no.
Ralf _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA