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 and was not
compatible with the latest noteboo
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 password nor do I recall the email address I used.
>
> Great to hear from you again!
Sec
On Wed, Feb 06, 2013 at 10:46:24PM +, John Cremona wrote:
> On 6 February 2013 22:02, Minh Nguyen wrote:
> > Hi Michael,
> >
> > 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 password nor do I recall
On Wednesday, February 6, 2013 4:41:25 PM UTC-5, Jean-Pierre Flori wrote:
>
> There's a ticket for valgrind upgrade to 3.8.1...
>
http://trac.sagemath.org/sage_trac/ticket/13060
> I guess it did not get merged because no one cares except a Mac user but
> there is some trouble on Apple^TM bec
>
>
> > 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 password nor do I recall the email address I used.
> >
> > Great to hear from you again!
>
> Seconded!
>
>
+1
--
You received thi
On 6 February 2013 22:02, Minh Nguyen wrote:
> Hi Michael,
>
> 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 password nor do I recall the email address I used.
>
> Great to hear from you again!
Seconded!
Jo
Hi Michael,
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 password nor do I recall the email address I used.
Great to hear from you again! I've reconfigured your trac account.
I'll contact you offlist about t
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 build it on such computers and not the FSF GCC Sage ships.
Anyway, I just installed it
Hello folks,
it has been a while, i.e.summer 2009 or so, and I no longer have my trac
account password nor do I recall the email address I used. Anyway, attached
is a patch that fixes sage -valgrind. Did not see any ticket on track, but
I noticed that at least the valgrind 3.8.1 spkg is coming
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), while
Yes, except you want to do it circularl
On Wed, Feb 6, 2013 at 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), while
> Parent.__init__ is execut
On Wed, Feb 6, 2013 at 11:39 AM, Robert Bradshaw
wrote:
> On Wed, Feb 6, 2013 at 11:07 AM, Simon King wrote:
>> PS:
>>
>> On 2013-02-06, Simon King wrote:
>>> But I wonder: It is a typical use case to add elements from A and B
>>> frequently and not only once. Do we really want that the parent C
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), while
Parent.__init__ is executed?
Cheers,
Simon
--
You received this message because yo
On Wed, Feb 6, 2013 at 11:07 AM, Simon King wrote:
> PS:
>
> On 2013-02-06, Simon King wrote:
>> But I wonder: It is a typical use case to add elements from A and B
>> frequently and not only once. Do we really want that the parent C may be
>> constructed repeatedly, unless the user keeps a manua
PS:
On 2013-02-06, Simon King wrote:
> But I wonder: It is a typical use case to add elements from A and B
> frequently and not only once. Do we really want that the parent C may be
> constructed repeatedly, unless the user keeps a manual strong reference
> to C or disables garbage collection?
I
Hi!
We are fixing more and more memory leaks. But I wonder if we went too
far in #14058.
Consider the following scenario: You have parents A, B, with elements
a,b. Assume that a+b lives in a parent C different from A and B,
obtained by sage.categories.pushout.pushout(A,B). A typical example is
A=
Travis Scrimshaw has done quite some work in adding *lots of doctests*
to sage/rings. All this work now needs a reviewer, before it get lost
again. My expectation is that it should be an easy (although long) review.
Here it is:
http://trac.sagemath.org/sage_trac/ticket/13618
--
You received th
Hello!
I have allowed myself to make some pretty aggressive changes to the graph
theory roadmap page.
http://trac.sagemath.org/sage_trac/wiki/GraphTheoryRoadmap
Feel free to revert it back to the previous state if you don't like its
current look!
Best regards,
Jernej
--
You received this m
18 matches
Mail list logo
