On Tue, 26 Oct 2010 at 06:44PM -0700, William Stein wrote: > Anyway, it has occurred to me (a few times, and again recently) that > it would be possible to make much of the Sage distribution, without > Python of course, into a Python library. What I mean is the following. > You would have a big Python library called "sagemath", say, and inside > of that would be a huge HG repository. In that repository, one would > check in the source code for many of the standard Sage spkg's... e.g., > GAP, Pari, etc. When you type > > python setup.py install > > then GAP, Pari, etc., would all get built, controlled by some Python > scripts, then installed as package_data in the sagemath directory of > <your python>/site-packages/.
Without commenting on your entire proposal, let me say that the idea of having all of Sage inside *one* Mercurial repo sounds very nice. When someone says "it worked in version 5.0!" I'd love to just do "hg up 5.0" and rebuild what has changed. That would make bisecting much more powerful, since right now "hg bisect" isn't very helpful with anything that involves different versions of a spkg. I know that the "rebuild what has changed" part presents a lot of difficulty, but the one-repo-to-rule-them-all idea is very nice. Dan -- --- Dan Drake ----- http://mathsci.kaist.ac.kr/~drake -------
signature.asc
Description: Digital signature
