Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On 30 April 2015 at 21:45, kcrisman wrote: > Bill Page wrote: >> It just occurred to me that for such >> simple things there should be simple solutions. And I guess there is: > > Well, that has been discussed a lot. There *is* one possibility now - you > can open a pull request at https://githu

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

> > Yes, I guess we do so at our own risk. :) My intention was not to > flame but rather just expressing my reaction after reading > > http://sagemath.org/doc/developer/git_trac.html#chapter-git-trac > > and considering the possible fate of my 3 line patch if I don't find > the time to do thin

[sage-devel] A __reduce__ function handling **kwargs

Hello everybody, I have a simple problem. I need to implement a __reduce__ function for pickling, and such a function must apparently return a pair: (f, args) You can then build the original object with "f(*args)". I would like to do the same, but with additional "keywords arguments", i.e.

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On Thu, Apr 30, 2015 at 2:52 PM, Bill Page wrote: >> I won't claim that Sage's >> doctests make Sage have "fewer errors or problems" than the other >> systems you use (they surely have their own approaches to testing). >> However, I absolutely claim -- and I'm sure anybody with nontrivial >> Sage

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On 30 April 2015 at 16:06, William Stein wrote: > On Thu, Apr 30, 2015 at 12:34 PM, Bill Page > wrote: >> ... > You stated 'that the Sage developer emphasis on "doc tests" has > resulted in any fewer errors or problems in Sage in comparison to > other systems.' I'm not sure if I should respon

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On Thu, Apr 30, 2015 at 12:34 PM, Bill Page wrote: > On 30 April 2015 at 13:34, Dima Pasechnik wrote: >> On Thursday, 30 April 2015 17:11:39 UTC+1, Bill Page wrote: >> ... >> well, for rants we have a special newsgroup called sage-flame. >> > > Yes, although I consider what I wrote more of an inc

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On 30 April 2015 at 13:29, Dima Pasechnik wrote: > On Thursday, 30 April 2015 18:12:00 UTC+1, Bill Page wrote: >> >> I just tested the patch and now I get the following in a Sage worksheet on >> SMC: >> >> axiom.eval(")version") >> >> 'alue = "Axiom Axiom (May 2012) built on Friday July 25, 2014 a

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On 30 April 2015 at 13:34, Dima Pasechnik wrote: > On Thursday, 30 April 2015 17:11:39 UTC+1, Bill Page wrote: > ... > well, for rants we have a special newsgroup called sage-flame. > Yes, although I consider what I wrote more of an inconvenient statement of fact so maybe I used the wrong tag. >

[sage-devel] Re: Why packages tarballs have to be in lowercase ?

It seems that a consensus on those issues should be reached *before* patching anything : the different behaviors of different platforms (Macs nvs other Unices, and do not forget Windows, which is still a target...) make some assumptions hardly enforceable (or even checkable). The scripts should

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On Thursday, 30 April 2015 17:11:39 UTC+1, Bill Page wrote: > > On 30 April 2015 at 05:29, Dima Pasechnik > > wrote: > > On Thursday, 30 April 2015 10:09:55 UTC+1, Dima Pasechnik wrote: > >> On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote: > >>> > >>> > PPS. if you really are pre

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On Thursday, 30 April 2015 18:12:00 UTC+1, Bill Page wrote: > > I just tested the patch and now I get the following in a Sage worksheet on > SMC: > > axiom.eval(")version") > > 'alue = "Axiom Axiom (May 2012) built on Friday July 25, 2014 at 23:34:17 > "\r\n' > > %sage > from axiom import a

[sage-devel] Re: Why packages tarballs have to be in lowercase ?

John H Palmieri wrote: > On Thursday, April 30, 2015 at 2:43:43 AM UTC-7, Jeroen Demeyer wrote: > > On 2015-04-30 08:57, Emmanuel Charpentier wrote: > > The Developer's guide > > > >

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

I just tested the patch and now I get the following in a Sage worksheet on SMC: axiom.eval(")version") 'alue = "Axiom Axiom (May 2012) built on Friday July 25, 2014 at 23:34:17 "\r\n' %sage from axiom import axiom axiom.eval(")version") 'Value = "Axiom Axiom (May 2012) built on Friday July 25,

Re: [sage-devel] Why packages tarballs have to be in lowercase ?

On Thursday, April 30, 2015 at 2:43:43 AM UTC-7, Jeroen Demeyer wrote: > > On 2015-04-30 08:57, Emmanuel Charpentier wrote: > > The Developer's guide > > < > http://www.sagemath.org/doc/developer/packaging.html#directory-structure> > > states the ported packages' tarballs have to be in *lower

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On 30 April 2015 at 05:29, Dima Pasechnik wrote: > On Thursday, 30 April 2015 10:09:55 UTC+1, Dima Pasechnik wrote: >> On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote: >>> >>> > PPS. if you really are pressed for time, I can submit this patch >>> > instead... >>> > >>> >>> Thanks I wou

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On 30 April 2015 at 05:29, Dima Pasechnik wrote: > ... >> >> I thought that on SMC in a Sage worksheet you can do %axiom >> and this will call a system-wide Axiom. Currently SMC is hanging for me, >> so I can't check. > > > OK, one can start axiom in an SMC terminal, by typing axiom > it is > (1)

[sage-devel] Re: Why packages tarballs have to be in lowercase ?

Jeroen Demeyer wrote: > On 2015-04-30 08:57, Emmanuel Charpentier wrote: >> The Developer's guide >> >> >> states the ported packages' tarballs have to be in *lower case* : >> "The build scripts and associated files are in a

[sage-devel] Re: Bug in pickling of callable symbolic functions

On Thursday, April 30, 2015 at 2:30:48 AM UTC-7, Eric Gourgoulhon wrote: > > Hi, > > I've recently faced this surprising appearance of a logarithm (in Sage > 6.7.beta3 as well as in any older versions I've tried, down to Sage 6.3): > > sage: var('y') > y > sage: f = function('H', x, y); f > H(x, y

Re: [sage-devel] Re: ask.sagemath.org login trouble

On Thu, Apr 30, 2015 at 8:27 AM, Nils Bruin wrote: > I'm having different trouble: I used to authenticate with Google open ID, > which doesn't work anymore. I tried "recover via email". It does recognize > my email addres and reports "Account recovery email sent". No mail seems to > arrive, thoug

[sage-devel] Re: ask.sagemath.org login trouble

I'm having different trouble: I used to authenticate with Google open ID, which doesn't work anymore. I tried "recover via email". It does recognize my email addres and reports "Account recovery email sent". No mail seems to arrive, though. -- You received this message because you are subscr

[sage-devel] ask.sagemath.org login trouble

I get an internal server error when I try to login with the password. Were there recent changes to the corresponding server? Dima -- 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, se

[sage-devel] Re: The high memory cost of creating many Polyhedron objects

On Tuesday, 17 February 2015 14:55:35 UTC, Nathann Cohen wrote: > > Hello everybody, > > I am trying to compute a couple of things on polyhedra, and for that I > need to generate and test a lot of them, each at a time. While I never > store them in any way my code stops after a while because o

Re: [sage-devel] Why packages tarballs have to be in lowercase ?

> On 30/04/2015, at 21:43, Jeroen Demeyer wrote: > > On 2015-04-30 08:57, Emmanuel Charpentier wrote: >> The Developer's guide >> >> states the ported packages' tarballs have to be in *lower case* : >> "The build scripts

Re: [sage-devel] Why packages tarballs have to be in lowercase ?

On 2015-04-30 08:57, Emmanuel Charpentier wrote: The Developer's guide states the ported packages' tarballs have to be in *lower case* : "The build scripts and associated files are in a subdirectory SAGE_ROOT/build/pkgs/pa

[sage-devel] Bug in pickling of callable symbolic functions

Hi, I've recently faced this surprising appearance of a logarithm (in Sage 6.7.beta3 as well as in any older versions I've tried, down to Sage 6.3): sage: var('y') y sage: f = function('H', x, y); f H(x, y) sage: loads(dumps(f)) -x*log(-x*y + 1) If we use a lower case symbol, it is fine: sage

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On Thursday, 30 April 2015 10:09:55 UTC+1, Dima Pasechnik wrote: > > > > On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote: >> >> >> On Apr 29, 2015 7:30 AM, "Dima Pasechnik" wrote: >> >> >> > >> >> > this patch should go into Sage proper, as it also fixes the same as >> with SMC >>

Re: [sage-devel] Re: Poll: Which objects should be plotted by default in the notebook?

> On the other hand, things that *are* plots should be plotted (duh) and if > you ask to "show" them, since the default behavior has been to plot and not > LaTeX, that should probably continue. Not exactly related, but here is the behaviour in beta3 (see [1] and [2]): sage: show(posets.ChainPoset

Re: [sage-cloud] Re: [sage-devel] Typeset output in non-Sage modes in Sage Notebook

On Wednesday, 29 April 2015 23:17:19 UTC+1, Bill Page wrote: > > > On Apr 29, 2015 7:30 AM, "Dima Pasechnik" > > wrote: > > >> > > >> > this patch should go into Sage proper, as it also fixes the same as > with SMC > >> > issue with Sage's notebook. > >> > > >> > >> Sure. What is the best

Re: [sage-devel] Re: GP out of memory while testing Sage-6.6

On 30 April 2015 at 01:51, leif wrote: > Andrey Novoseltsev wrote: >> I don't think I've seen it reported before: running "make ptestlong" on >> Sage-6.6 after distclean crashed my server last night. > > Similar has been reported to sage-release about two weeks ago: > > http://thread.gmane.org/gma

Re: [sage-devel] Heavy class rewrite and old pickles

Hi Nathann, There is a tiny bit of documentation in sage.structure.sage_object. Look in particular at register_unpickle_override that allows you to redefine how old pickles have to be pickled. There are tons of examples in the Sage library. Just grep register_unpickle_override. On the other hand,

[sage-devel] Heavy class rewrite and old pickles

Hellooo everybody, I come to you because I plan to (seriously) rewrite the internal strucure of graph classes. While this makes no difference on the outside, I am meeting problems with pickles: Indeed, there are two classes in sage.graphs.base.backends which are named (since 2010): - NetworkX