On 19 May 2015 at 17:15, David Cournapeau <courn...@gmail.com> wrote: > On Wed, May 20, 2015 at 12:46 AM, Paul Moore <p.f.mo...@gmail.com> wrote: >> >> On 19 May 2015 at 16:22, Chris Barker <chris.bar...@noaa.gov> wrote: >> > The other issue is social: this would really only be a benefit if a wide >> > variety of packages shared the same libs -- but each of those packages >> > is >> > maintained by different individuals and communities. So it's had to know >> > if >> > it would get used. I could put up a libpng wheel, for instance, and who >> > knows if the Pillow folks would have any interest in using it? or the >> > matplotlib folks, or, ... And this would be particularly difficult when >> > the >> > solution was hacked together... >> >> Honestly, I still haven't seen a solid explanation of why (at least on >> Windows) static linking isn't a viable option. > > > Because some libraries simply don't work as static libraries, or are too big > (MKL comes to mind). Also, we have been historically using static libs for > our eggs at Enthought on windows, and it has been a nightmare to support. It > just does not scale when you have 100s of packages. > > But really, once wheels support arbitrary file locations, this becomes > fairly easy at the packaging level: the remaining issue is one of ABI / > standards, but that's mostly a non technical issue. > > Gholke has 100s of packages using wheels, and we ourselves at Enthought have > close to 500 packages for windows, all packaged as eggs, maybe 30-40 % of > which are not python but libs, C/C++ programs, etc... It is more about > agreeing about a common way of doing things than a real technical > limitation.
Thanks. I'm not going to try to argue against the voice of experience. If you were saying dynamic libs were impossible with wheels (which has been a definite impression I've got elsewhere in this thread) I might try to argue, but if you're saying that the technical issues are solvable, then that's great. We need to establish the details of the "common way of doing things" that needs to be agreed to move forward. Maybe an interoperability PEP would be useful here, with someone simply proposing a solution to give the debate a concrete starting point? Paul _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
