sage

src/sage/repl/ipython_extension.py: https://github.com/sagemath/sage/blob/develop/src/sage/repl/... docs: https://doc.sagemath.org/html/en/reference/repl/sage/repl/ip... https://github.com/sagemath/sage/blob/develop/src/sage/repl/...

> They have other things to smooth out the parts of python I should add that this is an interesting chunk of Python code, and we've always planned to separate it out from Sage as a separate library than could be used with Sympy, etc. https://github.com/sagemath/sage/blob/52a81cbd161ef4d5895325... It does a surprising number of little clever things we realized would be a good idea over years, and it has some neat ideas from various Python PEP's like [1..10] that were rejected from Python, but are very useful when expressing mathematics. It's also annoying when you just want to format your code using prettier (say), and you can't because Sage isn't Python. :-(

RETHINKDB: - There is a recent discussion about whether or not RethinkDB is dead here: https://github.com/rethinkdb/rethinkdb/issues/6747 - Judging by new PR's and commits, Rethinkdb development slowed down substantially in Jan 2016. SAGEMATH: - SageMath development is still very active; maybe more so, due probably to strong Europe grant support (OpenDreamKit): https://github.com/sagemath/sage/graphs/contributors SAGEMATHCLOUD: What this blog post is "really" about. - We renamed it "CoCalc" -- https://cocalc.com - I rewrote everything that depended on RethinkDB using PostgreSQL. Though it was months of work, this was obviously a VERY good decision in retrospect! - I rewrote all the realtime sync functionality to not depend on the database at all (just use a custom protocol over websockets), which is obviously a much more scalable approac

I started Sage, and worked on it a huge amount 2004-2012, but less so recently (due to working mostly on CoCalc). Actual contributions to and work on Sage by the community have gone UP a lot since 2012, as this plot (https://github.com/sagemath/sage/graphs/contributors) at Github shows. Much of that work is from research mathematicians that are adding large swaths of important functionality (e.g., in differential manifolds) to Sage. But there's also a very welcome push for quality, e.g., the number one recent contributor, fchapoton, has been fixing every little detail in the codebase revealed by https://lgtm.com/ and other tools, and there's also been a lot of work to fully transition Sage to Python 3 (which is difficult since so much is written in Cython and make nontrivial use of comparisons). I would have likely made Sage pip-in

> how you think you can match the "cohesiveness" of Mathematica The basic strategy is to provide a new Python library ("the sage library" [1]), which is a layer between the user and the other dependencies. E.g., instead of just saying "use Maxima for symbolic limits", we have our own notion of symbolic functions (implemented using Ginac), and automatically convert them to and from Maxima when doing symbolic limits. The user never has to know anything about Maxima. When we first implemented this, it just used interprocess communication under the hood, but (thanks to Nils Bruin and others) we now use a direct C library interface builton top of ECL (embedded common lisp). This "new Python library", which isn't so new, since I started it in 2004, is now nearly a million lines of code. [1] https://github.com/sagemath/sage/tree/master/src/

At the very beginning (back in 2005) it was mostly a distribution, but during the last 12 years an enormous amount of new code (over 500K SLOC) has been written, building on top of that distribution. You can get a sense of the scale and velocity of development here: https://github.com/sagemath/sage/graphs/contributors

(I'm the guy who started Sage.) Sage has the Jacobi symbol as of 7 years ago (see https://trac.sagemath.org/ticket/11138 and https://github.com/sagemath/sage/blob/07d6c37d18811e2b377a96...). Sage is pretty good at primality testing, because PARI is. I'm really glad that the author of this library is enjoying writing Algebraic number theory that is readable and in Python3. Go for it, and have fun!

Thanks. In the meantime, see https://github.com/sagemath/sage/commits/master or https://git.sagemath.org/sage.git/

I was just checking recently, and was pleasantly surprised to see that the amount Sage development, has gone up enormously in the last 2 years, especially thanks to Europeans! https://github.com/sagemath/sage/graphs/contributors

1. I introduced the "Sage preparser", which does things like replacing "1/3" by "Integer(1)/Integer(3)" in Sage, before feeding that input to Python to be evaluated; Robert Bradshaw also did a lot of work on the preparer. The preparser uses a hook into the IPython evaluation system. I decided I really needed Sage to use a preparser like this during a talk I gave at Pycon 2005, based on audience feedback, which is why it exists. 2. I would really like somebody to remove the preparse code from Sage and make it a standalone library available on pypi. Here's the code (happy to relicense it under BSD): https://github.com/sagemath/sage/blob/master/src/sage/repl/p... 3. Permalink to your example -- http://sagecell.sagemath.org/?q=nwzdzn

There's a concrete object-oriented Python implementation of much of abstract algebra is Sage. You can see some of that here: https://github.com/sagemath/sage/blob/master/src/sage/struct... (Disclaimer: I'm a Sage developer.)

Sage also has its own 1.5 million line python/cython library that is part of Sage (https://github.com/sagemath/sage/tree/master/src/sage)