I'm afraid this isn't particularly cool looking but, here is some data and
a couple of charts:
https://docs.google.com/spreadsheet/ccc?key=0AkPdD0Nnsj7BdDBENDRxTVNtR3c2VEVPeWpSN3BvV1E
I was hoping to see some stronger trends, but I think due to the nature of
Sage development (Sage days etc.) ther
On Wednesday, December 26, 2012 3:27:43 PM UTC-5, Harald Schilly wrote:
>
>
>
> On Wednesday, December 26, 2012 8:24:14 PM UTC+1, Jan Groenewald wrote:
>>
>> The following 59 people contributed to this release. Of those, 4 made
>> their first contribution to Sage:
>>
>> Is there a graph of this o
On Wednesday, December 26, 2012 10:34:49 PM UTC+1, Jean-Pierre Flori wrote:
>
> But see
> https://groups.google.com/d/topic/cython-users/4es75DeacRA/discussion
> as well...
> I'll give this new Cython 0.17.3 a try.
And it is even packaged at
http://trac.sagemath.org/sage_trac/ticket/13832
--
But see
https://groups.google.com/d/topic/cython-users/4es75DeacRA/discussion
as well...
I'll give this new Cython 0.17.3 a try.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To u
On Wednesday, December 26, 2012 10:28:01 PM UTC+1, Jean-Pierre Flori wrote:
>
> And of course, I just found that...
> https://groups.google.com/d/topic/cython-users/K5EFvq22UNI/discussion
>
> But I'm not sure it actually solves our problem.
--
You received this message because you are subscribe
And of course, I just found that...
https://groups.google.com/d/topic/cython-users/K5EFvq22UNI/discussion
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this gr
On Wednesday, December 26, 2012 8:22:24 PM UTC+1, Jean-Pierre Flori wrote:
>
>
>
> On Wednesday, December 26, 2012 8:20:03 PM UTC+1, Jean-Pierre Flori wrote:
>>
>>
>>
>> On Wednesday, December 26, 2012 8:08:24 PM UTC+1, Jean-Pierre Flori wrote:
>>>
>>>
>>>
>>> On Wednesday, December 26, 2012 6:49
On 12/26/2012 11:23 AM, kcrisman wrote:
>
>
> On Wednesday, December 26, 2012 6:51:42 AM UTC-5, Jeroen Demeyer wrote:
>
> On 2012-12-25 20:22, Stephen Montgomery-Smith wrote:
> > When I am building sage-5.5 inside of sage-5.5
> What does this mean? If it means building Sage inside a
On Wednesday, December 26, 2012 8:24:14 PM UTC+1, Jan Groenewald wrote:
>
> The following 59 people contributed to this release. Of those, 4 made
> their first contribution to Sage:
>
> Is there a graph of this over time?
>
Not that I'm aware of. Therefore: the source data for this weeks Sage
Yar i do not undarstand u?
On 12/27/12, Jean-Pierre Flori wrote:
>
>
> On Wednesday, December 26, 2012 7:43:16 PM UTC+1, Jeroen Demeyer wrote:
>>
>> On 2012-12-26 19:04, Volker Braun wrote:
>> > * SAGE_DEBUG=no means no debugging symbols (no gcc -g), which
>> > basically only saves disk space.
Hi
The following 59 people contributed to this release. Of those, 4 made
their first contribution to Sage:
Is there a graph of this over time?
Regards,
Jan
--
.~.
/V\ Jan Groenewald
/( )\www.aims.ac.za
^^-^^
--
You received this message because you are subscribed to the Google
Hi
The following 59 people contributed to this release. Of those, 4 made
their first contribution to Sage:
Is there a graph of this over time?
Regards,
Jan
On Wednesday, 26 December 2012 14:57:52 UTC+2, Jeroen Demeyer wrote:
>
> Sage 5.5 was released on 21 December 2012. It is available in
On Wednesday, December 26, 2012 8:20:03 PM UTC+1, Jean-Pierre Flori wrote:
>
>
>
> On Wednesday, December 26, 2012 8:08:24 PM UTC+1, Jean-Pierre Flori wrote:
>>
>>
>>
>> On Wednesday, December 26, 2012 6:49:52 PM UTC+1, Jean-Pierre Flori wrote:
>>>
>>> The offending object seems to be a weakref w
On Wednesday, December 26, 2012 8:08:24 PM UTC+1, Jean-Pierre Flori wrote:
>
>
>
> On Wednesday, December 26, 2012 6:49:52 PM UTC+1, Jean-Pierre Flori wrote:
>>
>> The offending object seems to be a weakref which is not refcounted
>> correctly.
>> Not sure which yet.
>>
> Not sure why, but it mi
On Wednesday, December 26, 2012 6:49:52 PM UTC+1, Jean-Pierre Flori wrote:
>
> The offending object seems to be a weakref which is not refcounted
> correctly.
> Not sure which yet.
>
Not sure why, but it might be the one initialized by the Expect class at
the line:
quit.expect_objects.appe
On Wednesday, December 26, 2012 7:43:16 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2012-12-26 19:04, Volker Braun wrote:
> > * SAGE_DEBUG=no means no debugging symbols (no gcc -g), which
> > basically only saves disk space.
> >
> > * SAGE_DEBUG=yes builds debug versions if possible (in partic
On 2012-12-26 19:04, Volker Braun wrote:
> * SAGE_DEBUG=no means no debugging symbols (no gcc -g), which
> basically only saves disk space.
>
> * SAGE_DEBUG=yes builds debug versions if possible (in particular,
> Python and Singular). These will be notable slower but allow us to
> pinpoint mem
On Dec 26, 10:18 am, Nils Bruin wrote:
> Very minor mod: Also provide an assignable value for SAGE_DEBUG for
> the default behaviour, rather than relying on SAGE_DEBUG being unset.
> Probably SAGE_DEBUG='', unset SAGE_DEBUG and perhaps also
> SAGE_DEBUG='default' should have the same effect.
Neve
Forgot to add: This is http://trac.sagemath.org/sage_trac/ticket/13865
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsu
On Dec 26, 10:04 am, Volker Braun wrote:
> I propose
> that we use SAGE_DEBUG in three different ways:
[...]
+1. Obvious and easy to use.
Very minor mod: Also provide an assignable value for SAGE_DEBUG for
the default behaviour, rather than relying on SAGE_DEBUG being unset.
Probably SAGE_DEBUG=
Currently, SAGE_DEBUG is documented as
"If it is unset (the default) or set to 'yes', then debugging is turned
on."
As the "How to proceed to reduce Sage's memory leaking" thread shows, we
should make it easy for developers to build Python with debugging, which
has a certain performance im
The offending object seems to be a weakref which is not refcounted
correctly.
Not sure which yet.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, se
Pexpect is a nice trick if you want to get off the ground quickly in
interfacing another program, but the strategic goal should be to turn it
into a shared library or develop a RPC call library that we can plumb into
the source code. Your average scientific code is just a scanf/printf loop
so i
On Wednesday, December 26, 2012 6:51:42 AM UTC-5, Jeroen Demeyer wrote:
>
> On 2012-12-25 20:22, Stephen Montgomery-Smith wrote:
> > When I am building sage-5.5 inside of sage-5.5
> What does this mean? If it means building Sage inside a Sage shell,
> that's not supported and might indeed brea
On 2012-12-24 01:30, Francois Bissey wrote:
> Well there was a big commit to change the handling of the license 2
> months ago but the last commit before was 4 years ago I think.
> So for all purpose it looks abandoned. May be the author is waiting
> for someone interested?
pexpect is quite horrib
2012/12/26 Jeroen Demeyer
> * We closed 92 tickets in this release. For details, see
Awesome, I'm going to download it right now.
Too bad nobody wanted to review this trivial bugfix:
http://trac.sagemath.org/sage_trac/ticket/13649
--
*Andrea Lazzarotto* - http://andrealazzarotto.com*
*
--
On Wednesday, December 26, 2012 12:01:48 AM UTC+1, Jean-Pierre Flori wrote:
>
>
>
> On Tuesday, December 25, 2012 5:36:41 PM UTC+1, Jean-Pierre Flori wrote:
>>
>> In fact it seems you already segfault when going through the line
>> from sage.misc.all import * #takes a while
>> in sage/all.py,
>>
Sage 5.5 was released on 21 December 2012. It is available in
source and binary form from:
* http://www.sagemath.org/download.html
Sage (http://www.sagemath.org/) is developed by volunteers and combines
over 90 open source packages. For instructions about installing Sage, see
* http://www.sa
On 2012-12-25 20:22, Stephen Montgomery-Smith wrote:
> When I am building sage-5.5 inside of sage-5.5
What does this mean? If it means building Sage inside a Sage shell,
that's not supported and might indeed break.
--
You received this message because you are subscribed to the Google Groups
"sag
I thought that its a missing dependency at first, too. But then he's
compiling sage/libs/mpmath/ext_impl.c, which is a cython file from the Sage
library. That should be after all spkgs have been installed. In fact, it
seems to be the Sage port to FreeBSD so who knows how it is being built.
Prob
On 26/12/12 23:47, Dima Pasechnik wrote:
> On 2012-12-25, Stephen Montgomery-Smith wrote:
>> On 12/25/2012 01:22 PM, Stephen Montgomery-Smith wrote:
>>> When I am building sage-5.5 inside of sage-5.5, I get the following
>>> error in my build log. I was able to build sage-5.5.rc1 with no
>>> prob
On 2012-12-25, Stephen Montgomery-Smith wrote:
> On 12/25/2012 01:22 PM, Stephen Montgomery-Smith wrote:
>> When I am building sage-5.5 inside of sage-5.5, I get the following
>> error in my build log. I was able to build sage-5.5.rc1 with no
>> problem. Am I unique with this problem? I am buil
when testing 5.5, i got this exception. ubuntu 12.10, 64bit.
File
"/home/opt/sage/sage-5.5/devel/sage-main/sage/modular/modsym/space.py",
line 209:
sage: ModularSymbols(12,8).character()
Exception raised:
Traceback (most recent call last):
File "/home/opt/sage/sage-5.5/local/bin/nc
33 matches
Mail list logo
