python libraries

[parisse]

(04-23-2021 09:23 AM)jonmoore Wrote:  Bernard, out of interest. How much of Numpy and Scipi did you 'clone' for the Ndless version of XCAS/Giac?

It's hard to answer, because I do not know numpy and scipy myself. I just looked at some scripts for schools and tried to make them compatible. A little bit like Python syntax in Xcas, but I tested much less, because in the meantime I decided it was not worth the time required to have something more compatible. The guys who have imposed Python as the unique langage in French highschools are mostly closed-minded, they will probably never consider Xcas to be an alternative to Python for programming in math classes despite my efforts. And if are already using Xcas, it's much easier to run the native commands of Xcas than using all these Python modules.

Quote:And on the subject of Cython/Cpython, don't the developers of SageMath use the optimisations you discuss in your last post to optimise certain aspects of SageMath inclusive of those that utilise Giac?

Giac is interfaced to CPython with Cython, independently from Sage, you can import giacpy from Python if you install giacpy. I don't know if all C libraries are interfaced using cython inside Sagemath, probably.
My opinion is that Sagemath "Python as a common basis" choice is wrong, because if you want to use their code inside your code, then you must interface with Python. It means that C libraries inside Sagemaths can not talk together unless they have their own interface. Inside Sage, at the Python level, you can choose one algorithm or another one, but once you are in non Python code (e.g. Maxima code because Sage does not have calculus itself, or C code because Python is slow), you can not benefit from other parts of the whole system (for example your C code can not benefit from other C libraries included in Sage unless you wrote your own interface to these other C libraries, or Maxima code does not benefit from fast linear algebra). You must write Python code to benefit from Sage and it will be useful to Python programmers only.
I believe that the choice should have been to make C libraries talk together, because it does not make assumptions on the caller language.