Hi Felix, On Tue, Sep 8, 2009 at 2:47 AM, felix<fe...@neuro.uni-bremen.de> wrote:
<SNIP> > Furthermore, there are tickets regarding broken scipy 0.7.0 packages > when using python 2.6 which have been fixed since. Which tickets are you referring to? Can you give specific links to those tickets? > The sage packet index lists scipy 0.7.p2 whatever that means. Is this > supposed to be the latest version? The current version of SciPy in Sage 4.1.1 is 0.7 with some extra patches on top to make that version work with Sage. The suffix ".p2" means that three sets of patches have been applied on top of SciPy 0.7. > I haven't tried to compile sage with another version of scipy, I'm > currently just switching to sage 4.0.1 when I intend to use weave (I > only use it to test code fragments before I build proper extensions) > which is currently good enough for me to get my work done. The latest release is SciPy 0.7.1. If you want to see a newer version in Sage than what is currently shipped with Sage 4.1.1, all you need to do is create a ticket for that issue on the Sage trac bug tracking server at http://trac.sagemath.org/sage_trac Please email William Stein if you require a trac account. -- Regards Minh Van Nguyen --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
