That's probably because I know nothing about the issue, is there any reference I can read about? But in general, please feel free populate new items in the wiki page. On Sun, Jul 23, 2017 at 11:15 AM, Nathaniel Smith <njs@pobox.com> wrote:
I've been wishing we'd stop shipping Accelerate for years, because of how it breaks multiprocessing – that doesn't seem to be on your list yet.
A few months ago, I had the innocent intention to wrap LDLt decomposition routines of LAPACK into SciPy but then I am made aware that the minimum required version of LAPACK/BLAS was due to Accelerate framework. Since
I've been following the core SciPy team and others' discussion on this issue.
We have been exchanging opinions for quite a while now within various SciPy issues and PRs about the ever-increasing Accelerate-related issues and I've compiled a brief summary about the ongoing discussions to reduce the clutter.
First, I would like to kindly invite everyone to contribute and sharpen
cases presented here
https://github.com/scipy/scipy/wiki/Dropping-support-for-Accelerate
The reason I specifically wanted to post this also in NumPy mailing list is to probe for the situation from the NumPy-Accelerate perspective. Is
On Sat, Jul 22, 2017 at 3:50 AM, Ilhan Polat <ilhanpolat@gmail.com> wrote: then the there
any NumPy specific problem that would indirectly effect SciPy should the support for Accelerate is dropped?
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
-- Nathaniel J. Smith -- https://vorpus.org _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion