On 4/17/07, legout <[EMAIL PROTECTED]> wrote: > first thanks for your fast reply. > > > SageX is a fork of Pyrex, since the author of Pyrex wouldn't incorporate > > the many useful > > changes we had back into Pyrex. > > Thats the reason, why i would use sageX instead of pyrex. > > Another question. Is there a plan, to make sage compatible to python, > so that every python modul could be used inside of sage? > Or maybe the other way. Sage as a python modul. > Are there any ideas doin such things with sage? Or is this not > possible.
Actually, both are already the case, to some extent. First, if you get a Python package from the web, say as a tarball, which you would normally install by doing "python setup.py install", you should -- in many cases at least -- by able to do "sage -python setup.py install". If that works, then from sage you should be able to import the module that you just installed. There are often little issues that come up though... For scipy there is an optional package, so you can just do: sage -i scipy-2006-12-05 but you have to have FORTRAN for this to work. William --~--~---------~--~----~------------~-------~--~----~ 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-forum URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
