All I know is this:

1) We have "sold" a lot of Sage by saying it's all in there, and at least 
some people have used Sage+R effectively.  Estimates of how many vary 
wildly.  But non-zero.
2) rpy2 might be there, but as far as I can tell most people who've used 
Sage+R use it via the "dumb pexpect interface".
3) All those thousands of packages are darn useful and can't be easily 
replaced with pandas or anything else.
4) kernels are nice but how do you get Sage command line to do that?  I 
personally would only know how to do it, sort of, in Jupyter notebook, and 
not at all clear how to send stuff back and forth between Sage and R there.

My conclusion:

1) Definitely don't remove R from Sage, unless we go back on the mission 
statement.  We want to be able to easily use all those extra packages with 
algebra and graph theory.  (Not to mention current users.)
2) Finding a way to deprecate (!!!) current R behavior is viable, but 
should be a longer-than-normal period.  Including graphics and other stuff. 
 If rpy2 is the answer, great; I recall it being deemed not as satisfactory 
at some point but maybe no one ever tried since pexpect was "good enough".
3) Excellent idea to integrate pandas or whatever the current flavor of the 
month is far better!
4) But if no one is willing/able/whatever to make these new interfaces, 
keeping pexpect is definitely far better than simply jettisoning R.

(Note e.g. people who have used Sage cell server to embed R graphics in web 
pages - not sure how that would be affected, if it's a separate R process 
or via Sage?)

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to