Mon Apr 28 02:45:26 CDT 2008
As far as I am concerned, the issue needs a cosmetic fix of renaming
pythonxerbla to python_xerbla and the rest of the issue can be
postponed to 1.2.
Note that this isn't purely a numpy issue. To fix the
issue, system or user provided blas/lapack libraries need to be changed,
we can only give instructions how to do that. Doing the change
automatically requires testing the corresponding support code for many
different platforms and setups - this requires some effort and time..
and most importantly, some volunteers.
Jarrod Millman wrote:
> On Wed, Apr 9, 2008 at 6:34 AM, Stéfan van der Walt <firstname.lastname@example.org> wrote:
>> Unfortunately, I couldn't get this patch to work, and my time has run
>> out. Maybe someone with more knowledge the precedences/order of
>> functions during linking can take a look. I don't know how to tell
>> the system BLAS to call our custom xerbla, instead of the one
>> The patch addresses an important issue, though, so it warrants some
>> more attention.
> I was wondering what the status of this ticket is? Is this something
> that should be fixed before 1.1.0?
More information about the Numpy-discussion