Release 4.0 is soon. So I suggest we split the work. 1) Update R to the latest 2.9 release (ticket #3086) I have no development experiences, but I assume that updating is a straightforward activity (but maybe I'm wrong).
2) Loading common packages in advance. After release 4.0 we look how many users have the same needs. If its really worthwhile, we can consider to take the next step. Roland On 2 mei, 09:30, William Stein <wst...@gmail.com> wrote: > On Sat, May 2, 2009 at 12:26 AM, Rolandb <rola...@planet.nl> wrote: > > > Hi > > > Ticket #3086 states "Update R to the 2.7 release and split off > > rpy.spkg" with milestone Sage 4.0. > > > If possible, two requests: > > > 1) Update R to the latest 2.9 release (now sage 3.4 uses R version > > 2.6.1 (2007-11-26)) > > > 2) To use R one has to load various additional packages. For instance > > I use the following lines: > > > import rpy > > pack=["abind", "distr", "distrEx", "e1071", "effects", "foreign", > > "grid", "lattice", "lmtest", "MASS", "mgcv", "multcomp","Rcmdr"] > > for p in pack: r.install_packages(p) > > > As the policy of Sage is "all inclusive", I suggest rpy includes the > > most common R packages. > > > Thanks in advance! > > Is there any chance you could help with making the above happen? You > might be the biggest user of R in Sage in the world. > > William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
