#14706: r-project : because it's that time of the semester, again...
----------------------------------------------------------------+-----------
Reporter: charpent |
Owner: jdemeyer
Type: enhancement |
Status: needs_review
Priority: trivial |
Milestone: sage-5.11
Component: packages: standard |
Resolution:
Keywords: r-project spkg | Work
issues:
Report Upstream: None of the above - read trac for reasoning. |
Reviewers:
Authors: | Merged
in:
Dependencies: |
Stopgaps:
----------------------------------------------------------------+-----------
Changes (by charpent):
* status: new => needs_review
Comment:
* '''Status''' changed from ''new'' to ''needs_review''
1) New spkg : available on Google drive
(https://docs.google.com/file/d/0B1gfn4_V_wm3clctVFFhUnlINVU/edit?usp=sharing)
2) What this ticket is about :
a) Having an up-to-date R is a sine qua non to get answers from R Core.
b) R in Sage is rarely up to date (more talented Sage developers work on
more important issues).
c) Therefore, R-in-Sage users have trouble communicating with R Core
d) 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...
e) 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.
Is that clearer ?
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14706#comment:5>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
