On Friday, November 22, 2013 3:47:16 PM UTC+13, William wrote: > > On Thu, Nov 21, 2013 at 6:40 PM, kcrisman <kcri...@gmail.com <javascript:>> > wrote: > > > > > > On Thursday, November 21, 2013 3:08:44 PM UTC-5, François wrote: > >> > >> On Thu, 21 Nov 2013 09:54:10 Jason Grout wrote: > >> > On 11/21/13 9:35 AM, kcrisman wrote: > >> > > I love that the Sage cell supports it (there was a fascinating blog > >> > > post > >> > > about embedding R a year or so ago), ... it would be very, very > >> > > unfortunate if we were to drop support for this. > >> > > >> > Just to be clear: the Sage cell would *certainly* still have R (along > >> > with many other optional and even just plain python packages [1]). > >> > > >> Another option that could be interesting, sage doesn't use or link > >> against the R library so it is trivial to actual use a system wide R. > > I don't believe this. Sage includes and builds rpy2, which is vastly > superior to our pexpect interface to R for working with nontrivial > data, and rpy2 links against the R library. Unfortunately, it would > (in my experience) be very difficult to get > > import rpy2 > rpy2.do_stuff > > to work on all supported platforms if we don't build our own version of R. >
You are right I completely overlooked two libraries in rpy2. It indeed makes things difficult since R can be linked to an external blas amongst other thing. So much for that idea. On the subject of the time taken to compile R: R itself compiles in parallel relatively fast. But then you compile the standard R packages, it is all serial and some are quite slow. Francois -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
