<div dir="ltr">On Sat, May 16, 2015 at 12:04 PM, David Mertz <span dir="ltr"><<a href="mailto:dmertz@continuum.io" target="_blank">dmertz@continuum.io</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Continuum has a great desire to make 'pip' work with conda packages. Obviously, we love for users to choose the Anaconda Python distribution but many will not for a variety of reasons (many good reasons).</div></blockquote><div><br></div><div>Hmm -- this strikes me as very, very , tricky -- and of course, tied in to the other thread I've been spending a bunch of time on...<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>However, we would like for users of other distros still to be able to benefit from our creation of binary packages for many platforms in the conda format. </div></div></blockquote><div><br></div><div>Frankly, if you want your efforts at building binaries to get used outside of Anaconda, then you shoudl be building wheels in the first place. While conda does more than pip + wheel can do -- I suppose you _could_ use wheels for the things it can support..<br><br></div><div>But on to the technical issues:<br><br></div><div>conda python packages depend on other conda packages, and some of those packages are not python packages at all. The common use case here are non-python dynamic libs -- exactly the use case I've been going on in the other thread about...<br><br></div><div>And conda installs those dynamic libs in a conda environment -- outside of the python environment. So you can't really use a conda package without a conda enviroment, and an installer that understands that environment (I think conda install does some lib path re-naming, yes?), i.e. conda itself. So I think that's kind of a dead end.<br><br></div><div>So what about the idea of a conda-package-to-wheel converter? conda packages an wheels have a bit in common -- IIUC, they are both basically a zip of all the files you need installed. But again the problem is those dependencies on third party dynamic libs. <br><br></div><div>So far that to work -- pip+wheel would have to grow a way to deal with installing, managing and using dynamic libs. See the other thread for the nightmare there...<br><br></div><div>And while I'd love to see this happen, perhaps an easier route would be for conda_build to grow a "static" flag that will statically link stuff and get to somethign already supported by pip, wheel, and pypi.<br><br></div><div>-Chris<br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>It is true that right now, a user can in principle type:</div><div><br></div><div> % pip install conda</div><div> % conda install some_conda_package</div><div><br></div><div>But that creates two separate systems for tracking what's installed and what dependencies are resolved;</div></div></blockquote><div><br></div><div>Indeed -- which is why some folks are working on making it easier to use conda for everything....converting a wheel to a conda package is probably easier than the other way around..<br> <br></div><div>Funny -- just moments ago I wrote that it didn't seem that anyone other than me was interested in extending pip_wheel to support this kind of thing -- I guess I was wrong!<br><br></div><div>Great to see you and continuum thinking about this.<br></div><div><br><br></div><div>-Chris<br><br></div></div>-- <br><div class="gmail_signature"><br>Christopher Barker, Ph.D.<br>Oceanographer<br><br>Emergency Response Division<br>NOAA/NOS/OR&R (206) 526-6959 voice<br>7600 Sand Point Way NE (206) 526-6329 fax<br>Seattle, WA 98115 (206) 526-6317 main reception<br><br><a href="mailto:Chris.Barker@noaa.gov" target="_blank">Chris.Barker@noaa.gov</a></div>
</div></div>