On Tue, Jun 23, 2009 at 12:23 AM, Tom Boothby wrote:
>
> Progress Report:
>
> I've gotten a massive response from reviewers, thank you all very
> much! I'm using Craig Citro's new automerge script, which has both
> made it very easy, and very frustrating, to apply patches. Easy
> because it down
On Jun 21, 2009, at 12:54 PM, John Cremona wrote:
> 2009/6/21 William Stein :
>>
>> On Sun, Jun 21, 2009 at 8:38 PM, gsw
>> wrote:
>>>
>>> Hi John,
>>>
>>> On 21 Jun., 17:47, John Cremona wrote:
This should be of interest to anyone who has ever had to manage
precision issues between
On Tue, Jun 23, 2009 at 12:04 AM, Dan Drake wrote:
> On Mon, 22 Jun 2009 at 10:00PM -0600, Ondrej Certik wrote:
>> Sometimes if the code is very recursive, I use a hand made debugging
>> printing using decorators --- I decorate each function I want to debug
>> and it prints a nice tree like graph,
On Jun 21, 2009, at 8:21 AM, William Stein wrote:
> 2009/6/21 gsw :
>>
>> On 21 Jun., 15:54, William Stein wrote:
>>> 2009/6/21 Bjarke Hammersholt Roune :
>>>
>>>
>>>
I quote from
>>>
http://www.sagemath.org/doc/developer/inclusion.html
>>>
which is about the inclusion procedure
On Jun 22, 2009, at 11:44 AM, Nicolas M. Thiery wrote:
> On Thu, Jun 18, 2009 at 09:29:46AM -0700, Nicolas Thiéry wrote:
>> On Thu, Jun 18, 2009 at 04:40:50PM +0200, William Stein wrote:
>>> On Thu, Jun 18, 2009 at 9:03 AM, Nicolas M.
To ease the reviewing of the category code, and also to m
On Mon, 22 Jun 2009 at 10:00PM -0600, Ondrej Certik wrote:
> Sometimes if the code is very recursive, I use a hand made debugging
> printing using decorators --- I decorate each function I want to debug
> and it prints a nice tree like graph, so it's easy to check things,
> e.g:
>
> SYMPY_DEBUG=Tr
On Jun 22, 2009, at 2:25 AM, Franco Saliola wrote:
>
> Hello,
>
> Here is a quick description of what is below: Subclasses of Element
> complain that no sorting algorithm is defined even when all the rich
> comparison methods have been implemented. Bug?
>
> In the code sample below, C is a class
Dear all,
Apparently, there is a convention emerging to name systematically all
patches on trac as trac__description.patch. I very much value this
standardization attempt, especially in a period where things are
getting automatized. We need it! In particular, I find it very useful
to
Nope, since I didn't know about it.
Which is why Martin's presentation is such a good idea. ;-)
Rob
On Jun 22, 9:07 pm, Jason Grout wrote:
> Rob Beezer wrote:
> > 2. I very often use search_src('def foo(') to discover where, and
> > how, the function foo is implemented. Might not be ob
On Mon, Jun 22, 2009 at 10:00 PM, Ondrej Certik wrote:
> On Thu, Jun 18, 2009 at 11:50 AM, Carlo
> Hamalainen wrote:
>>
>> Hi,
>>
>> I'm curious about which debugging environment is most popular among
>> the Sage developers?
>>
>> * print statements only (ugh)
>> * pdb
>> * ddd
>> * Eric4
>> * som
On Thu, Jun 18, 2009 at 11:50 AM, Carlo
Hamalainen wrote:
>
> Hi,
>
> I'm curious about which debugging environment is most popular among
> the Sage developers?
>
> * print statements only (ugh)
> * pdb
> * ddd
> * Eric4
> * something else?
I use print statements, sometimes I use the following tr
Rob Beezer wrote:
> 2. I very often use search_src('def foo(') to discover where, and
> how, the function foo is implemented. Might not be obvious to those
> who are new to Python, yet still want to explore the code.
Have you used search_def()?
Jason
--~--~-~--~~--
Robert Miller wrote:
> print, think, print, think, print, think, fix
>
Same here, except there are usually a few more print, think iterations.
Occasionally I turn to pdb as well.
At one point I also used Eclipse (not with Sage, with another python
project). That was really nice.
Jason
--~
On Jun 22, 11:46 am, Rob Beezer wrote:
> 2. I very often use search_src('def foo(') to discover where, and
> how, the function foo is implemented. Might not be obvious to those
> who are new to Python, yet still want to explore the code.
[...]
> 4. It took me a while to discover that d
> There is another problem, which is that currently, the web page seems
> to indicate (although not directly) that the code is released under
> GPLv3.
Wait a tic, the distribution itself has a LICENSE file which clearly
says that the code is GPLv2. One less thing, I guess...
--~--~-~--~
On Tue, Jun 23, 2009 at 12:25 AM, Ondrej Certik wrote:
>
> On Mon, Jun 22, 2009 at 3:25 AM, Franco Saliola wrote:
>>
>> Hello,
>>
>> Here is a quick description of what is below: Subclasses of Element
>> complain that no sorting algorithm is defined even when all the rich
>> comparison methods hav
Nathann,
I've taken a look at the Cliquer source, as well as your spkg. I'm
CC'ing Bjarke Roune and Martin Albrecht, who have been taking a look
at this as well, here in Barcelona. I also am sending this to
sage-devel, since it is clear we need a second, third, fourth
opinion...
It is actually u
The problem is probably the space between "ngens" and the parenthesis.
David
On Mon, Jun 22, 2009 at 1:30 PM, Simon King wrote:
>
> Hi William,
>
> On Jun 22, 6:33 pm, William Stein wrote:
> > It's not a proper parser. It's just a quick "hack" that goes through
> > the text file and grabs """
>> do we need to get a secondary reviewer in that case?
>
> I would be fine reviewing those back, if this sounds reasonable to the
> others.
The cycle of submit, reviewer resubmit, original implementor reviews
resubmission has been accepted for a long time; I see no reason to
change.
Nick
-
On Mon, Jun 22, 2009 at 3:25 AM, Franco Saliola wrote:
>
> Hello,
>
> Here is a quick description of what is below: Subclasses of Element
> complain that no sorting algorithm is defined even when all the rich
> comparison methods have been implemented. Bug?
If it helps, I create this page, that l
Progress Report:
I've gotten a massive response from reviewers, thank you all very
much! I'm using Craig Citro's new automerge script, which has both
made it very easy, and very frustrating, to apply patches. Easy
because it downloads & applies patches in bulk, frustrating because it
has bugs a
On Mon, Jun 22, 2009 at 05:35:15PM -0400, David Roe wrote:
> So, I can certainly do that by Wednesday.
Great.
> I think much of the difficulty will be getting the code up to 100%
> doctest coverage. It's not really feasible for Nicolas to write all
> those doctests.
Yeah. Part of the thing is:
On Mon, Jun 22, 2009 at 11:35 PM, David Roe wrote:
> So, I can certainly do that by Wednesday. I think much of the difficulty
> will be getting the code up to 100% doctest coverage. It's not really
> feasible for Nicolas to write all those doctests. I'm happy to contribute
> doctests for my sec
So, I can certainly do that by Wednesday. I think much of the difficulty
will be getting the code up to 100% doctest coverage. It's not really
feasible for Nicolas to write all those doctests. I'm happy to contribute
doctests for my section; do we need to get a secondary reviewer in that
case?
D
On Mon, Jun 22, 2009 at 7:29 PM, Justin C. Walker wrote:
>
>
> On Jun 18, 2009, at 10:26 , Craig Citro wrote:
>
>>
>> Hi all,
>>
>> Here's rc3, which *should* be the last rc for this release cycle. I've
>> tested it on my laptop and the build farm, and I've had no troubles at
>> all, and it's curr
On Mon, Jun 22, 2009 at 6:43 PM, Nick Alexander wrote:
>
>
> On 22-Jun-09, at 9:38 AM, Robert Miller wrote:
>
>>
>> I tried running the Sage notebook as follows, from SAGE_ROOT/devel/
>> sage-main:
>>
>> $ ../../sage -notebook
>>
>> And I get the following error:
>>
>> Please wait while the Sage N
On Thu, Jun 18, 2009 at 09:29:46AM -0700, Nicolas Thiéry wrote:
> On Thu, Jun 18, 2009 at 04:40:50PM +0200, William Stein wrote:
> > On Thu, Jun 18, 2009 at 9:03 AM, Nicolas M.
> > > To ease the reviewing of the category code, and also to make it more
> > > generic and useful, I have extracted the
Dear Tom, dear category reviewers,
On Sat, Jun 20, 2009 at 02:30:23PM -0700, Nicolas Thiéry wrote:
> On Fri, Jun 19, 2009 at 12:00:19PM -0700, Tom Boothby wrote:
> > I'm the release manager for sage-4.0.3.
> > Python to 2.6, and if I succeed, I'll rename the release to sage-4.1.
> > In ab
On Mon, Jun 22, 2009 at 11:25:32AM +0200, Franco Saliola wrote:
> Here is a quick description of what is below: Subclasses of Element
> complain that no sorting algorithm is defined even when all the rich
> comparison methods have been implemented. Bug?
>
> In the code sample below, C is a class
http://trac.sagemath.org/sage_trac/ticket/6385
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http:
Hi William,
On Jun 22, 6:33 pm, William Stein wrote:
> It's not a proper parser. It's just a quick "hack" that goes through
> the text file and grabs """ (triple quoted strings). It even would
> break if you use ''' instead of """.
I hope you didn't take offense in what I wrote!
> Somebody,
On Jun 18, 2009, at 10:26 , Craig Citro wrote:
>
> Hi all,
>
> Here's rc3, which *should* be the last rc for this release cycle. I've
> tested it on my laptop and the build farm, and I've had no troubles at
> all, and it's currently going on a few other machines, so hopefully
> that'll turn out
2009/6/22 Nick Alexander :
>
>
> On 22-Jun-09, at 9:38 AM, Robert Miller wrote:
>
>>
>> I tried running the Sage notebook as follows, from SAGE_ROOT/devel/
>> sage-main:
>>
>> $ ../../sage -notebook
>>
>> And I get the following error:
>>
>> Please wait while the Sage Notebook server starts...
>>
On 22-Jun-09, at 9:38 AM, Robert Miller wrote:
>
> I tried running the Sage notebook as follows, from SAGE_ROOT/devel/
> sage-main:
>
> $ ../../sage -notebook
>
> And I get the following error:
>
> Please wait while the Sage Notebook server starts...
> Traceback (most recent call last):
> File
PS - I'm on a MacBook running OS 10.5.7, and
sage: notebook()
works fine.
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more optio
On Mon, Jun 22, 2009 at 6:38 PM, Robert Miller wrote:
>
> I tried running the Sage notebook as follows, from SAGE_ROOT/devel/
> sage-main:
>
> $ ../../sage -notebook
>
> And I get the following error:
>
> Please wait while the Sage Notebook server starts...
> Traceback (most recent call last):
>
I tried running the Sage notebook as follows, from SAGE_ROOT/devel/
sage-main:
$ ../../sage -notebook
And I get the following error:
Please wait while the Sage Notebook server starts...
Traceback (most recent call last):
File "/Users/rlmill/sage-4.0.2/local/bin/sage-notebook", line 9, in
On Mon, Jun 22, 2009 at 6:15 PM, Simon King wrote:
>
> Dear William,
>
> On Jun 22, 2:20 am, William Stein wrote:
>> sage -coverage file.py
>>
>> I wrote the first version of that script during a docday so I could
>> figure out what to doctest. It subsequently got traction.
>
> Thank you, that c
Dear William,
On Jun 22, 2:20 am, William Stein wrote:
> sage -coverage file.py
>
> I wrote the first version of that script during a docday so I could
> figure out what to doctest. It subsequently got traction.
Thank you, that comes at the right time for me...
Fortunately, it also seems to w
Below is a python script that implements the above and sets
environment variables for parallel compiles. Just save the script to
makesage.py (say) in the sage root dir and run it via
python makesage.py -j8
It reduced the sage-4.0.2 compile to 1hour 51 minutes on a dual quad
AMD 2GHz machine.
--
Hi Golam,
On Sat, 20 Jun 2009 10:07:33 -0300
Golam Mortuza Hossain wrote:
>
> Hi,
>
> I am wondering whether there is any policy/framework
> for hooking-up a specialized integration code as a part
> of integration algorithm in new symbolic?
There isn't any, yet. That should change this week
Sage works on slax-linux-6.2 (slackware Linux).
By the ways, I will distribute a live DVD/cdrom Linux in ICMCT9,
http://www.ictmt9.org. In which, Sage-4.0.1 is contained with other
CAS, octave, Maxima, Axiom and others. In particular, Sage worked with
Maxima-5.18.1.
The introduction of Live Linux
print, think, print, think, print, think, fix
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http:/
On Jun 22, 12:13 pm, Martin Albrecht
wrote:
> I will not say 'no' to that! Thank you! Can you prepare it as an SVG graphic
> so that I can adapt the colour if needed?
yes sure, i hope i have some time to do it today -- and i suppose you
want lcars design ;)
h
--~--~-~--~~--
On Monday 22 June 2009, Harald Schilly wrote:
> On Jun 22, 12:46 am, Martin Albrecht
>
> wrote:
> > Hi,
> >
> > as mentioned earlier I am preparing a talk on how to get started with
> > Sage development for Tuesday here at SD16. A first rc for my set of
> > slides is at:
> >
> >http://sage.ma
Hi there,
> Very nice! It's been on my Sage to-do list for some time to attempt
> something similar for the wiki or the developer's guide. At a
> minimum, I hope this presentation can get a pointer from the wiki
> (once its completed) from someplace other than just the SD16 pages.
Yes, definit
Hi Craig,
On 21 Jun., 23:32, Craig Citro wrote:
> Hi Georg,
>
> > The root cause was the patch for trac #2513 which was incorporated in
> > Sage-4.0.2.alpha4, concerning the setting (or not ...) of the variable
> > LANG in the sage-env script.
>
> > I'll prepare a nice patch with some explanatio
On Jun 22, 12:46 am, Martin Albrecht
wrote:
> Hi,
>
> as mentioned earlier I am preparing a talk on how to get started with Sage
> development for Tuesday here at SD16. A first rc for my set of slides is at:
>
> http://sage.math.washington.edu/home/malb/talks/sagedev.pdf
Looks good, and I hop
Hello,
Here is a quick description of what is below: Subclasses of Element
complain that no sorting algorithm is defined even when all the rich
comparison methods have been implemented. Bug?
In the code sample below, C is a class that inherits from Element and
implements all the rich comparison
> It still seems rather dull to be honest. I'd appreciate any input.
>
>
You could always try walking them through the process by fixing a bug live
during the talk. I think William did this in his class last quarter, with
mixed results. It'd definitely be exciting, though. I don't know if you're
al
On Sun, Jun 21, 2009 at 11:46:19PM +0100, Martin Albrecht wrote:
> as mentioned earlier I am preparing a talk on how to get started with Sage
> development for Tuesday here at SD16. A first rc for my set of slides is at:
>
>http://sage.math.washington.edu/home/malb/talks/sagedev.pdf
>
> It
51 matches
Mail list logo
