On Sat, Aug 4, 2012 at 12:14 PM, Aron Ahmadia <
aron@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.