Changes between Version 275 and Version 287 of Ticket #9808


Ignore:
Timestamp:
10/14/10 20:23:20 (11 years ago)
Author:
jhpalmieri
Comment:

Updates: my doctest failure in citation.pyx is a "red herring". In particular, it's not because of the patches here; it's because of a flaw in how the function get_systems works. Often when I've been testing the packages and patches on this ticket, I've created a new version of sage in a directory called "numpy", and get_systems sees that string in the path name and adds "numpy" to the systems used by the particular command. If I rename the directory to something else, then the doctest passes. So let's not worry about this; at some point, someone can fix get_systems so it ignores the initial chunk of the path name (ignore the parent of SAGE_ROOT, for example).

My doctest failure in matrix1.pyx is still there. For some reason, the "Datetime" type codes are not there on some systems. Any ideas why? I glanced at the install log for numpy, but I didn't see anything suspicious, not that I really know what to look for. Here's the log from my OS X 10.6 machine, which is one place I see this problem: http://sage.math.washington.edu/home/palmieri/misc/numpy-1.5.0.log.

Finally, I have a new version of the scipy spkg, which works for me on all of the machines I've tested on: linux, OpenSolaris, Solaris on x86, Mac OS X 10.6. I'm putting the link in the ticket description, and I'm posting the Mercurial patch -- it's very small.

I'm leaving this as "needs work" because of the matrix1.pyx issue, but I think that's the only remaining problem. Please test the new scipy spkg on other systems to make sure, though.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9808

    • Property Status changed from needs_review to needs_work
  • Ticket #9808 – Description

    v275 v287  
    44http://sage.math.washington.edu/home/kcrisman/numpy-1.5.0.spkg
    55
    6 http://boxen.math.washington.edu/home/kirkby/patches/scipy-0.8.spkg
     6http://sage.math.washington.edu/home/palmieri/SPKG/scipy-0.8.spkg
    77
    8 However, these changes have made it necessary to update the scipy_sandbox package too (#10092), which now has positive review and is in Sage 4.6.alpha3.
     8If you are applying these to any version before Sage 4.6.alpha3, then you also have to update the scipy_sandbox package too (#10092).  This has been merged in 4.6.alpha3, though.
    99
    10 http://boxen.math.washington.edu/home/kirkby/patches/scipy_sandbox-20071020.p6.spkg
     10http://boxen.math.washington.edu/home/kirkby/patches/scipy_sandbox-20071020.p7.spkg
    1111
    1212After installing Numpy, one needs to execute sage -ba, or do
     
    1414touch $SAGE_LOCAL/lib/python/site-packages/Cython/Includes/numpy.pxd
    1515}}}
    16 or else one will get runtime warnings. (Or if someone wants less hassle, they can patch sage-4.6.alpha2.spkg before building Sage).
     16or else one will get runtime warnings. (Or if someone wants less hassle, they can patch sage-4.6.alpha3.spkg before building Sage).
    1717
    1818trac_9808_numpy_doctest_change.patch in the attachment has to be applied, in order to get all doctests running because some of the output has changed.