#16299: upgrade numpy/scipy to 1.8.1 and 0.14
-------------------------------------+-------------------------------------
Reporter: fbissey | Owner:
Type: enhancement | Status: positive_review
Priority: major | Milestone: sage-6.3
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers: Nathan Dunfield
Authors: François Bissey | Work issues:
Report Upstream: N/A | Commit:
Branch: | 5a161248dd34be17b790e79a00414354abf0311f
u/fbissey/numpy181 | Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Changes (by dunfield):
* status: needs_review => positive_review
Comment:
I did a little testing, and definitely the issue is a result of the scipy
upgrade and not the numpy one. It also shows up on OS X version 10.8 as
well.
My experience is that the last digit in numerics like this can be
remarkably sensitive to the OS/CPU/compiler version/phase of the moon. I
once had two Ubuntu 12.04 virtual machines running on the same physical
hardware where the last digit differed like this; one had a 32bit kernel
and the other a 64bit one, which you wouldn't think would make a
difference...
I think this sort of thing is to be expected, and it certainly seems
harmless enough in this instance. So I've changed the status back to
"positive review".
--
Ticket URL: <http://trac.sagemath.org/ticket/16299#comment:15>
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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
