#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):
It would be nice but it may not be what we want. The only way to feed your
user configuration whatever it is is to set those variables to `None`. I
did this in #20157 and the goal is to have the user choice respected
whatever they are. You can read the description in #20157, without
disabling everything, I could get whatever is found first in the list
rather than what I want. Note that at least one new implementation has
been added to the list in 1.11 if I am not mistaken (`bliss`).
As far as I am concerned `numpy` should take user's wishes first and work
out what it is if it can.
--
Ticket URL: <http://trac.sagemath.org/ticket/20507#comment:1>
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.
