On 1 Nov., 07:51, William Stein <wst...@gmail.com> wrote: > This post is about: > > (1) Concern about distutils/setuptools/etc., is misplaced. > (2) Python3 and librarifying Sage. > > First, all this discussion about distutils/setuptools/david > cournapeau, etc., is actually mostly IRRELEVANT to making the core > Sage library into a standalone library.
That's an argument (honestly). Distutils/Setuptools is broken (or weird), so we don't [have to] use it. Not very "pythonic" though, I guess... ;-) (but nobody should be forced to drive with broken wheels) > [...] > 2. A function in setup.py builds all the non-standard C/C++ libraries > that the core Sage library depends on, which is the following 24 > libraries: > > boost-cropped givaro libm4ri mpir ratpoints > cliquer gsl libpng ntl > eclib iml linbox pari singular > ecm lcalc mpfi polybori symmetrica > flint libfplll mpfr pynac zn_poly > [...] I'd prefer having plain text files rather than a pickled build_db. Adding (formal) dependency specifications to the spkgs (a file, say, spkg-deps in each spkg) would be a step forward, too, such that we can also *generate* the "real Makefile" spkg/standard/deps in the traditional build process. (In addition, a lot of what's currently performed in every spkg- install could be factored out.) -Leif > [...] Thus if we wanted a Python3 version > of the Sage library itself, if we had a library like I describe above, > this would only require a Python3 version of numpy and networkx, plus > the work of porting the Sage library itself. This doesn't sound so > far off, since there already is a Python3 version of numpy. -- 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
