[Numpy-discussion] Moving away from using accelerate framework on mac os x ?

Ralf Gommers ralf.gommers at gmail.com
Sun Aug 5 12:31:03 EDT 2012

On Sat, Aug 4, 2012 at 2:36 PM, David Cournapeau <cournape at gmail.com> wrote:

> On Sat, Aug 4, 2012 at 12:14 PM, Aron Ahmadia <aron at ahmadia.net> wrote:
> > Hi David,
> >
> > Apple's response here is somewhat confusing, but I will add that on the
> > supercomputing side of things we rarely fork, as this is not
> well-supported
> > from the vendors or the hardware (it's hard enough to performantly spawn
> > 500,000 processes statically, doing this dynamically becomes even more
> > challenging).  This sounds like an issue in Python multiprocessing
> itself,
> > as I guess many other Apple libraries will fail or crash with the
> > fork-no-exec model.
> >
> > My suggestion would be that numpy continue to integrate with Accelerate
> but
> > prefer a macports or brew supplied blas, if available.  This should
> probably
> > also be filed as a wont-fix bug on the tracker so anybody who hits the
> same
> > problem knows that it's on the system side and not us.
> To be clear, I am not suggesting removing support for linking against
> accelerate, just to go away from it for our binary releases.

Would there be any issues when mixing for example a numpy built against
ATLAS with a scipy built against Accelerate?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20120805/a833f1ab/attachment.html>

More information about the NumPy-Discussion mailing list