[sage-devel] Re: Egg-path error in installing Sage 5.6

2013-02-07 Thread Keshav Kini
Kwankyu Lee writes: > Hi Keshav, > > > I was wondering what could be causing your problem but didn't > comment > because I didn't have a solution. > > > I still don't know exactly what caused the problem, but I suspect the > notebook files stored under ~/.sage was somehow out of date a

[sage-devel] Re: Fix busted sage -valgrind

2013-02-07 Thread mabshoff
On Thursday, February 7, 2013 3:48:01 AM UTC+1, jason wrote: > > On 2/6/13 7:26 PM, kcrisman wrote: > > > > > On Thu, Feb 7, 2013 at 8:13 AM, mabshoff > > wrote: > > >> it has been a while, i.e.summer 2009 or so, and I no longer have > > my trac > > >> account passwor

[sage-devel] Re: Fix busted sage -valgrind

2013-02-07 Thread mabshoff
On Wednesday, February 6, 2013 10:41:25 PM UTC+1, Jean-Pierre Flori wrote: > > There's a ticket for valgrind upgrade to 3.8.1... > I guess it did not get merged because no one cares except a Mac user but > there is some trouble on Apple^TM because it is coded so that only Apple > copimler can b

[sage-devel] Re: To what extent should pushouts be cached?

2013-02-07 Thread Simon King
Hi Travis, On 2013-02-07, Travis Scrimshaw wrote: >I think a tutorial on coercion would be useful (in particular, one on > how to implement the coercion model; maybe there is already one and I just > haven't found it yet...), That's exactly the purpose of my worksheet. More precisely: How

[sage-devel] Re: To what extent should pushouts be cached?

2013-02-07 Thread Simon King
Hi Jean-Pierre, On 2013-02-07, Jean-Pierre Flori wrote: > I would suggest to duplicate the info :) > Of course that's twice as much work. That' not twice as much. At least some of the text could be copy-and-pasted, even though an explanation in sage.structure.coerce would have a different audie

[sage-devel] Re: To what extent should pushouts be cached?

2013-02-07 Thread Travis Scrimshaw
> OK, that's what Robert did anyway, in #14073. He states there: "I don't >> think this code should go in unless it's clearly shown to be a problem." >> I guess that's a good idea. First wait if there is really a problem to >> fix. >> >> We could also include the code but somehow disabled, or

[sage-devel] Re: To what extent should pushouts be cached?

2013-02-07 Thread Travis Scrimshaw
Hey, In any case, I think it should be clearly documented that, for good > performance, one should avoid cross-parent arithmetic operations > altogether, or one should at least keep a pointer to the parent of the > result. > > But where should I put such a warning? I don't think > sage.struct

[sage-devel] Re: To what extent should pushouts be cached?

2013-02-07 Thread Jean-Pierre Flori
On Thursday, February 7, 2013 2:19:51 PM UTC+1, Simon King wrote: > > Hi, > > On 2013-02-06, Nils Bruin > wrote: > > On Feb 6, 12:05 pm, Simon King wrote: > >> There is the idea to always keep the last N created parents alive by a > >> strong reference. Couldn't this easily be done, by appen

[sage-devel] Re: To what extent should pushouts be cached?

2013-02-07 Thread Simon King
Hi, On 2013-02-06, Nils Bruin wrote: > On Feb 6, 12:05 pm, Simon King wrote: >> There is the idea to always keep the last N created parents alive by a >> strong reference. Couldn't this easily be done, by appending "self" to a >> list (and removing the first entry, when the list is too long), wh

[sage-devel] Sage builds and (almost) passes dockets on ARM chromebook

2013-02-07 Thread Charles Bouillaguet
Hi sage-lovers, You'll be happy to know that Sage builds out-of-the-box on a (samsung) ARM Chromebook running ubuntu. All but 3 doctests pass. The remaining 3 are numerical accuracy errors. I've opened http://trac.sagemath.org/sage_trac/ticket/14077 for those who are interested. Cheers, --- C