[sage-devel] Re: sage-edu, standard API, etc.

2008-02-25 Thread William Stein
On Mon, Feb 25, 2008 at 7:01 AM, didier deshommes <[EMAIL PROTECTED]> wrote: > > On Sat, Feb 23, 2008 at 1:24 PM, William Stein <[EMAIL PROTECTED]> wrote: > > I'm actually pretty curious about how pexpect and XMLRPC both > > done locally compare speedwise. I've done some simple benchmarks >

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-25 Thread didier deshommes
On Sat, Feb 23, 2008 at 1:24 PM, William Stein <[EMAIL PROTECTED]> wrote: > I'm actually pretty curious about how pexpect and XMLRPC both > done locally compare speedwise. I've done some simple benchmarks > below. The short answer is that pexpect is between several hundred > to several thous

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-24 Thread alex clemesha
On Sun, Feb 24, 2008 at 12:13 AM, William Stein <[EMAIL PROTECTED]> wrote: > > On Sat, Feb 23, 2008 at 11:59 PM, alex clemesha <[EMAIL PROTECTED]> > wrote: > > > > > > > > > > On Sat, Feb 23, 2008 at 10:24 AM, William Stein <[EMAIL PROTECTED]> > wrote: > > > > > > > > > On Sat, Feb 23, 2008 at 9:3

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-24 Thread Carl Witty
On Feb 23, 11:59 pm, "alex clemesha" <[EMAIL PROTECTED]> wrote: > First off, thanks for doing those benchmarks, > they are pretty interesting to see! > > I want to stress that I think that this API discussion > should really *not* have anything to do with speed, > and this is precisely because of

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-24 Thread William Stein
On Sat, Feb 23, 2008 at 11:59 PM, alex clemesha <[EMAIL PROTECTED]> wrote: > > > > > On Sat, Feb 23, 2008 at 10:24 AM, William Stein <[EMAIL PROTECTED]> wrote: > > > > > > On Sat, Feb 23, 2008 at 9:39 AM, alex clemesha <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > On Sat, Feb 23, 2008 at 12:0

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-24 Thread mabshoff
Hello, I am limiting myself to less than one email per day in this thread :) On Feb 23, 2:58 pm, kcrisman <[EMAIL PROTECTED]> wrote: > I think, though I'm not sure, that mabshoff has perhaps misunderstood > my points, probably because my post was too long, for which I > apologize. As I said, t

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-23 Thread alex clemesha
On Sat, Feb 23, 2008 at 10:24 AM, William Stein <[EMAIL PROTECTED]> wrote: > > On Sat, Feb 23, 2008 at 9:39 AM, alex clemesha <[EMAIL PROTECTED]> wrote: > > > > > > > > On Sat, Feb 23, 2008 at 12:02 AM, didier deshommes <[EMAIL PROTECTED]> > > wrote: > > > > > > > > > On Fri, Feb 22, 2008 at 5:57

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-23 Thread William Stein
On Sat, Feb 23, 2008 at 9:39 AM, alex clemesha <[EMAIL PROTECTED]> wrote: > > > > On Sat, Feb 23, 2008 at 12:02 AM, didier deshommes <[EMAIL PROTECTED]> > wrote: > > > > > > On Fri, Feb 22, 2008 at 5:57 PM, alex clemesha <[EMAIL PROTECTED]> wrote: > > > In Knoboo we *decouple* the idea of a kernel

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-23 Thread alex clemesha
On Sat, Feb 23, 2008 at 12:02 AM, didier deshommes <[EMAIL PROTECTED]> wrote: > > On Fri, Feb 22, 2008 at 5:57 PM, alex clemesha <[EMAIL PROTECTED]> wrote: > > In Knoboo we *decouple* the idea of a kernel, it could be another > > Python (Sage) process, with communication through Pexpect > > > > ..

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-23 Thread kcrisman
I think, though I'm not sure, that mabshoff has perhaps misunderstood my points, probably because my post was too long, for which I apologize. As I said, this post was very much in the conciliatory spirit of Jason Grout's original one. In particular, I was emphatically not addressing any of the

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-23 Thread didier deshommes
On Fri, Feb 22, 2008 at 5:57 PM, alex clemesha <[EMAIL PROTECTED]> wrote: > In Knoboo we *decouple* the idea of a kernel, it could be another > Python (Sage) process, with communication through Pexpect > > ... but it also couple be another Python (Sage) process running a very > minimal XML-RPC ser

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-22 Thread mabshoff
On Feb 23, 3:38 am, kcrisman <[EMAIL PROTECTED]> wrote: Hi, Du to lack of time and need for sleep I will only touch a couple issue. > Great thanks are due to Jason G. for starting to distill some of the > issues involved in the developments leading to sage-edu in a very > gracious manner. I h

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-22 Thread kcrisman
Great thanks are due to Jason G. for starting to distill some of the issues involved in the developments leading to sage-edu in a very gracious manner. I hope to add, in a similar vein (nothing about APIs, sorry!), more commentary on some more of the underlying issues, and a request to the "main d

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-22 Thread alex clemesha
On Fri, Feb 22, 2008 at 10:56 AM, David Joyner <[EMAIL PROTECTED]> wrote: > > On Fri, Feb 22, 2008 at 1:09 PM, Jason Grout > <[EMAIL PROTECTED]> wrote: > > > > Wow, this discussion blew up way to fast for me to keep on top of it > and > > form a coherent opinion. Ted, I'm specifically CCing you

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-22 Thread Robert Bradshaw
Thanks, Jason, for the lengthy reply. I think it summarizes things nicely. I started a simple API at the AMS meeting in January, and I think the time is ripe to have a discussion about this. I'll start a new thread summarizing my ideas (probably on sage-edu) when I have a bit more time (p

[sage-devel] Re: sage-edu, standard API, etc.

2008-02-22 Thread David Joyner
On Fri, Feb 22, 2008 at 1:09 PM, Jason Grout <[EMAIL PROTECTED]> wrote: > > Wow, this discussion blew up way to fast for me to keep on top of it and > form a coherent opinion. Ted, I'm specifically CCing you; if you don't > want to reply (either on or off list), I understand. Personally, I'd