[sage-devel] Yet another update ro Sage's R

The R core group has released R 3.1.1, which seems to be mostly a bugfix. This new version is ported to sage by trac#16711 , which await your reviews. HTH, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Grou

Re: [sage-devel] Re: Notebook login - upper case letters

You can add a warning to the file (based on your error, I am giving the file path): /usr/lib64/python2.7/site-packages/sagenb/data/sage/html/login.html Find the lines Sign into the Sage Notebook v{{ sage_version }} and append the following warning below it Note that the user name is case

[sage-devel] Re: Curious problem with Sage "fat_binary" tarballs

Le jeudi 24 juillet 2014 01:38:54 UTC+2, kcrisman a écrit : > > > > SAGE_FAT_BINRAY is quite fragile. >> If you really want me to, I can break it on quite every system. >> Are the machine really different? >> Maybe its just a problem with R and can be fixed. >> >> > I think that is quite likely a

[sage-devel] Re: Curious problem with Sage "fat_binary" tarballs

Le mercredi 23 juillet 2014 22:59:54 UTC+2, Jean-Pierre Flori a écrit : > > SAGE_FAT_BINRAY is quite fragile. > If you really want me to, I can break it on quite every system. > Are the machine really different? > Yes. I have a good laptop (core I7, 16 GB RAM), but my pinchy employer insists on

[sage-devel] Re: git-trac guessing remote branch skips one letter

I think this has been fixed a while ago. Pull the newest version of the git-trac script... On Wednesday, July 23, 2014 5:33:58 AM UTC-4, Daniel Krenn wrote: > > I was working on > > krenn@brown:/local/data/krenn/sage/current6$ git branch --contains > * article-fsm-in-sage > > and then wa

[sage-devel] Re: Have problem with R Interpreter

> > I use the following code but failed. > ### > x=[1,2,3,4,5] > y=[2,3,4,5,6] > x=r(x) > y=r(y) > r.t_test(x,y,alternative="less") > ### > It returns that error:object 48 not found > But it works if I didn't use alternative. > r.t_test(x,y) will ret

Re: [sage-devel] Re: Notebook login - upper case letters

Is it possible to patch Notebook somehow to make it show the clear error message (like "User does not exist.") and a hint (somethink like "Please check the upper case letters in login name" or "Please note that Sage Notebook distinguishes between lower case and upper case letters in login name")?

[sage-devel] no syntax highlighting in documentation at lines string with ....:

Dear all, probably you've noticed that there is no syntax highlighting for multi-line commands in the documentation (from the second line on). Is there a reason, why this is not fixed (since a couple of releases)? (I've tried to find a trac-ticket for it.is there any?) Best wishes Daniel

Re: [sage-devel] Re: "Groups" in Sage

Hel !! > Well, the question should be whether Sage supports Cartesian products. Then perhaps it should be named "set_cartesian_product" until this is fixed ? > This comes from CategoryObject and there's a TODO to refactor it out into > the proper category, but that would need everyth

[sage-devel] Re: very slow arithmetic in cartesian_product of fields

Perhaps the question is how to speed up the Cartesian product of rings in the case of rings being small, without resorting to having internal structures which would basically use addition and multiplication tables.That is, Cartesian product should be smart enough to dispatch the case of componen

Re: [sage-devel] On scientific computing, Python and Julia

On 24 July 2014 04:22, Robert Bradshaw wrote: > On Wed, Jul 23, 2014 at 5:47 PM, rjf wrote: >> >> >> On Saturday, July 19, 2014 8:22:39 AM UTC-7, Nils Bruin wrote: >>> >>> On Saturday, July 19, 2014 5:43:57 AM UTC-7, defeo wrote: However, Julia multimethods are backed up by a powerful c