#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):
If I set `ATLAS` to something more useful then it will look for something
I'm feeding it.
Like I said in the original ticket, it's a minor but confusing annoyance
that Numpy tells me it can't find ATLAS even when it is using ATLAS. I
agree it doesn't matter for the end result, but it makes it impossible to
read the build log and determine what BLAS implementation Numpy did find.
This is even more confusing when configuring SciPy.
Is there some discussion you could refer me to where it was decided what
the best way should be to configure BLAS for Sage? Because somewhere
along the line you probably *do* know what you're using. And if you don't
then you're using ATLAS since that's what Sage builds by default. So
there's no reason for Numpy to report something inaccurate.
As I wrote in my previous comment if I know I'm using ATLAS and I unset
the `ATLAS` environment variable then the issue is resolved. What the
`spkg-install` is doing currently removes context from the Numpy
configuration unnecessarily.
--
Ticket URL: <http://trac.sagemath.org/ticket/20507#comment:4>
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.
