Changes between Initial Version and Version 6 of Ticket #14706


Ignore:
Timestamp:
06/08/13 20:14:24 (8 years ago)
Author:
jdemeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #14706

    • Property Keywords spkg added
    • Property Status changed from new to needs_review
  • Ticket #14706 – Description

    initial v6  
    1 This ticket is a place where I plan to send new updates to the R version used in Sage (R is, in principle, updated every six months). So I intend to open, close, reopen... as long as newer versions '''do not entail any substantial modification''' beyond dropping new R source in place and fixing the expected version numbers in the r.py doctest. Any further problems should be reported in '''specific''' tickets. As a new R version arrives (and Real Life (TM) allowing), I'll start from the last accepted patch for this spkg...
     1a) Having an up-to-date R is a sine qua non to get answers from R Core.
    22
    3 This is routine work (i. e. even I can do it:-), but using an up-to-date R interpreter is a ''sine qua no''n for reporting problems to R core, so it probably has to be done for Sage users to get answers from R core.
     3b) R in Sage is rarely up to date (more talented Sage developers work on more important issues).
     4
     5c) Therefore, R-in-Sage users have trouble communicating with R Core
     6
     7d) I am able to create "drop-in replacements" of the R spkg, thus giving R-in-Sage users an up-to-date R, thus allowing them to get answers from R Core...
     8
     9e) Since this is routine work that few people seem to tackle, and since it is in my limited ability range, I'll try to do it after R upstream upgrades.