On Saturday, October 21, 2017 at 11:08:26 PM UTC+1, François Bissey wrote: > > > > On 22/10/2017, at 10:53, Dima Pasechnik <dim...@gmail.com <javascript:>> > wrote: > > rpy2 is installable using pip (I don't know its requirements); I suppose > it's maintained well, so the only issue here is of technical kind, pointed > out by Francois: libR, the R library needed by rpy2, links > against system blas/lapack (assuming R is provided by the system), and > this can cause various hiccups by conflicting with blas/lapack supplied by > Sage. > > > For the record I am not sure that’s such a big deal. I used to think it > was, but more experience dealing with shared objects on linux tells > me it probably isn’t. Probably OK on OS X not sure on windows. > We could just check for R in configure and build or not rpy accordingly. > People interested should look at the mess that is giac out of the box > (and in vanilla sage). > > That’s supposing rpy isn’t fundamentally needed in other part of sage > of course. >
no, rpy is not used anywhere in Sage, apart from sage/stats/r.py > > François > -- 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.
