Hi, I have been looking at upgrading numpy again in #11334 Everything seem to build fine but the doctest failures reveal some possibly deep problems.
In several tests a numpy array is prepared with numpy.linspace (there are at least two in functions/other.py). Then a function is appled to the numpy array, the function identifies the array as a numpy array and applies the numpy version of the function to it and fails. The failure is caused by the fact that the aray is not an array of numerical numpy types but an array of numpy object. the numpy.linspace function created a numpy array populated with objects some of which are of sage types and because of this the numpy functions are failing. With numpy-1.5.1 the same sequence of command was populating the numpy array with something that had a numpy numerical type and numpy knew out to deal with it. Not anymore. You can look at #11334 for some details but I am wondering where we go from there. We can cast the numpy array to something numpy understand but then we have to be careful of what it is and apply it in a lot of spots. Any ideas? Francois This email may be confidential and subject to legal privilege, it may not reflect the views of the University of Canterbury, and it is not guaranteed to be virus free. If you are not an intended recipient, please notify the sender immediately and erase all copies of the message and any attachments. Please refer to http://www.canterbury.ac.nz/emaildisclaimer for more information. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
