#9808: Upgrade numpy to 1.4.1 and scipy to 0.8
-----------------------------------+----------------------------------------
Reporter: maldun | Owner: maldun
Type: task | Status: needs_work
Priority: major | Milestone: sage-4.6
Component: packages | Keywords: numpy, scipy
Author: Stefan Reiterer | Upstream: N/A
Reviewer: Karl-Dieter Crisman | Merged:
Work_issues: |
-----------------------------------+----------------------------------------
Comment(by fbissey):
Replying to [comment:93 kcrisman]:
> Look in the same place, just posted it. So nice to be operating at 1.25
GHz instead of 700 MHz...
>
> Also, interestingly, I now have a "mixed" installation on this computer:
> {{{
> sage: import numpy
> sage: numpy.version.version
> '1.5.0'
> sage: import scipy
> sage: scipy.version.version
> '0.7.0'
> }}}
> At least some of the relevant tests seem to pass with this, though of
course I get the RunTimeErrors mentioned above and did `Inf` and `inf`
change places? I know little about numpy and scipy, though. Anyway,
that's better than on the other box, whose issues with bad tarballs seem
to not exist on this box.
Found the logs, I may have a theory and the logs may help to (in)validate
it.
Not sure about Inf/inf either. scipy should work fine with numpy-1.5 -
once rebuilt,
and sage needs rebuilding too. That may get rid of some of these runtime
errors.
scipy-0.8 needs numpy-1.4 minimum on the other hand.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9808#comment:94>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
