On 2/11/15 19:27, Andrey Novoseltsev wrote:
Option 3 is probably the best technically, and both Sage cell and SMC
(and IPython) could use it. It is hard technically to implement, and
would also require waiting a while until it actually gets into Sage.
It's even harder socially, since technically it isn't really doing
anything, but you have to get several people to agree on an API.
Often patches to sage take months (or more) from when they are
basically done to when they get into Sage, due our current pace of
development (since we have very little money and most work is done in
people's spare time). Due to things being slow, if there's one extra
new thing about Sage that needs to be changed for SMC or SageCell, and
there's no hook in the plugin mechanism for it (e.g., change
pretty_print), then you have to do either 1 or 2 *and* also 3, and
then switch out 1 or 2 for 3 later when it eventually gets into Sage.
That's not fun. If Sage releases happened much more frequently
(like every week or two, like they used to), then this wouldn't be a
problem. But these days stable Sage releases happen maybe every 3
months. It might get worse, since our release manager is going to be
much busier with other things (besides Sage) soon.
Yet meanwhile, in his negative spare time, he is making steady progress
to 3: http://trac.sagemath.org/ticket/17234 and some already merged tickets.
Current changes for the cell server are definitely less invasive/more
understandable than what they've used to be and I am full of hopes for
the summer.
Cool! With the cell server, we originally started with option 1 while
we were figuring out exactly what changes we needed to make, with the
goal of doing (3). We gradually progressed towards (3) (i.e., making
patches to Sage that could be incorporated upstream, particularly
https://github.com/novoselt/sage/commit/dc6fa50ab128a738c132c9fd10ac19b8b02b4dcc
and
https://github.com/novoselt/sage/commit/39026796cae1d101102bf693a44853a8b405e395,
which provide frameworks for us to plug in alternate implementations for
display routines, etc.), but we didn't get there. What Volker is doing
looks much more ambitious, though, and it's great to see it happening.
Jason
--
You received this message because you are subscribed to the Google Groups
"sage-gsoc" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-gsoc.
For more options, visit https://groups.google.com/d/optout.
