On Wednesday, August 27, 2014 4:16:46 PM UTC+2, bluescarni wrote: > > My impression is that the Scipy-Numpy-Sympy ecosystem is a better fit than > Sage, at least for numerical purposes. >
Mine too, and despite Sage lacking with updates there is nobody holding you back from working with just that stack in Sage and access additional features on demand. We should make sure that installing additional packages via pip does work (hence, we have to update numpy/scipy and so on from time to time to get pandas&co working) but besides that this is fine. There are only two major issues: * compatibility: e.g. the .numpy() of a sage matrix gives you something for numpy. one has to know that. * out-of-the-box: The Sage preparser breaks an awful lot of things if you do not know that it is transforming your input. Personally, I was never very fond of it but I fully understand why it is there. Me dreaming: All of the above could be solved by yet another additional sage spkg, which does not only add many of the numerical python libs, but also changes some of the internals (like, disabling the preparser). The actual question would be if that triggers any interest. I don't think so... --H -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
