#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 embray):
I think those are fine goals to have, and are not necessarily
contradictory with what I'm proposing--in fact the opposite. If there
were a clearer way during a build of sage+dependencies to specify which
BLAS implementation is being built with, it wouldn't be necessary to
disable detection of that library in Numpy, Scipy, or anything else that
uses `numpy.distutils`.
In other words, it would be good to configure Sage at build time what BLAS
it's using in such a way that it can pass that on to other packages as
well in case they do care, or just for the sake of provenance / reporting.
In the meantime this *can* be sort of done in the limited case of ATLAS,
albeit in a somewhat fragile sense, by checking for `-latlas`. If/when
Sage improves support for other libraries that could be handled on a case-
by-case basis.
--
Ticket URL: <http://trac.sagemath.org/ticket/20507#comment:6>
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.
