#20507: Slight annoyance wrt Numpy and ATLAS
---------------------------------+-------------------
Reporter: embray | Owner:
Type: defect | Status: new
Priority: minor | Milestone:
Component: PLEASE CHANGE | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
---------------------------------+-------------------
Comment (by fbissey):
The means used by `numpy`sucks. Why do you even need to know which
blas/lapack you are using? For `ATLAS` it means that `numpy` may use
`ATLAS` c interface to lapack - well if you want to do that may be you
should look for lapacke instead, something with a standard interface.
The point being, if you are after blas/lapack functions, they are standard
and you shouldn't worry about the implementation underneath. `numpy`'s
mechanism is a cute way (at best) to try various known libraries in a
given order of preference. My preference would be for `numpy` to start
looking for something I feed it before/rather than trying autodetection.
--
Ticket URL: <http://trac.sagemath.org/ticket/20507#comment:3>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
