#9808: Upgrade numpy to 1.5.0 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, Francois Bissey, John Palmieri, David Kirkby
| Upstream: Fixed upstream, but not in a stable release.
Reviewer: Karl-Dieter Crisman, David Kirkby, Leif Leonhardy, Francois
Bissey | Merged:
Work_issues:
|
----------------------------------------------------------------------------------+
Comment(by kcrisman):
Here is something relevant in the latest Scipy - is it in previous version
(in INSTALL.TXT)? This might obviate the need to specify all those
fortran compiler options...
{{{
You can specify which Fortran compiler to use by using the following
install command::
python setup.py config_fc --fcompiler=<Vendor> install
To see a valid list of <Vendor> names, run::
python setup.py config_fc --help-fcompiler
}}}
Is there somewhere in Scipy's makefile (or whatever) that specifies the
architecture stuff for the super-universal binary? I don't think that
other Sage spkgs have the ppc64 arch, and I don't see anything in `spkg-
install` that would do this. Anyway, the thing about not finding
certain fortran compilers in John's log looks suspicious, perhaps.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9808#comment:246>
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.
