[sage-devel] Re: sage.math hd space bimonthly consumption contest - November winners :)

On Mon, Nov 24, 2008 at 6:33 PM, Ronan Paixão <[EMAIL PROTECTED]> wrote: > > Em Seg, 2008-11-24 às 16:15 -0800, mabshoff escreveu: >> >> >> On Nov 23, 6:23 pm, Ronan Paixão <[EMAIL PROTECTED]> wrote: >> > Em Dom, 2008-11-23 às 03:13 -0800, mabshoff escreveu:> Hello folks, >> >> Hi, >> >> > > we ne

[sage-devel] Re: sage.math hd space bimonthly consumption contest - November winners :)

Em Seg, 2008-11-24 às 16:15 -0800, mabshoff escreveu: > > > On Nov 23, 6:23 pm, Ronan Paixão <[EMAIL PROTECTED]> wrote: > > Em Dom, 2008-11-23 às 03:13 -0800, mabshoff escreveu:> Hello folks, > > Hi, > > > > we nearly ran out of space on /home for the first time in a while. The > > > following

[sage-devel] Re: sage.math hd space bimonthly consumption contest - November winners :)

On Nov 23, 6:23 pm, Ronan Paixão <[EMAIL PROTECTED]> wrote: > Em Dom, 2008-11-23 às 03:13 -0800, mabshoff escreveu:> Hello folks, Hi, > > we nearly ran out of space on /home for the first time in a while. The > > following accounts are using more than 1GB space and on case your name > > is one

[sage-devel] Re: [Bulk] [sage-devel] sage.math hd space bimonthly consumption contest - November winners :)

Em Dom, 2008-11-23 às 03:13 -0800, mabshoff escreveu: > Hello folks, > > we nearly ran out of space on /home for the first time in a while. The > following accounts are using more than 1GB space and on case your name > is one the list you should consider cleaning up unused files. > This should l

[sage-devel] Re: timeit limitations?

On Mon, Nov 24, 2008 at 2:47 PM, Simon King <[EMAIL PROTECTED]> wrote: > > Dear Tim, > > On Nov 24, 8:41 pm, "Tim Lahey" <[EMAIL PROTECTED]> wrote: >> var('x') >> f = 2*x/sin(x)^2 >> f.integrate(x) >> axiom.integrate(f,x) >> timeit(f.integrate(x)) >> timeit(axiom.integrate(f,x)) > > AFAIK, unlike

[sage-devel] Re: Python 2.6

On Mon, Nov 24, 2008 at 01:59:04PM -0800, William Stein wrote: > > On Mon, Nov 24, 2008 at 1:37 PM, Jason Grout > <[EMAIL PROTECTED]> wrote: > > Okay, good, so you are looking at these things. Securely executing > > python is a subject with a long history. Recent developments include > > the as

[sage-devel] Re: Python 2.6

On Nov 24, 1:59 pm, "William Stein" <[EMAIL PROTECTED]> wrote: > On Mon, Nov 24, 2008 at 1:37 PM, Jason Grout > > <[EMAIL PROTECTED]> wrote: > > Okay, good, so you are looking at these things.  Securely executing > > python is a subject with a long history.  Recent developments include > > the a

[sage-devel] Re: Python 2.6

William Stein wrote: > On Mon, Nov 24, 2008 at 1:37 PM, Jason Grout > <[EMAIL PROTECTED]> wrote: >> Okay, good, so you are looking at these things. Securely executing >> python is a subject with a long history. Recent developments include >> the ast module, though I think the high-level ast modu

[sage-devel] Python 2.6

On Mon, Nov 24, 2008 at 1:37 PM, Jason Grout <[EMAIL PROTECTED]> wrote: > Okay, good, so you are looking at these things. Securely executing > python is a subject with a long history. Recent developments include > the ast module, though I think the high-level ast module is just in 2.6, > and so

[sage-devel] Re: A simpler SAGE?

jrpick wrote: > For security, I just mean that if I have it running on a server, I > don't want people to be able to do malicious things like play with the > filesystem, send mail, or drop mysql tables. More than a sandbox, > however: you shouldn't be able to disable it, or otherwise mess things

[sage-devel] From the Maxima list:

Saw this on sci.math.symbolic and thought it might be of interest to Maxima users and developers. Ray ___ Maxima mailing list [EMAIL PROTECTED] http://www.math.utexas.edu/mailman/listinfo/maxima --

[sage-devel] Re: addressing notion impedance

>> Why not to do such translations (from a polynomial to a polynomial) >> transparently to the user? > > The section you looked at is actually a pretty ugly example indeed and > with the current Sage getting objects from one system to another is > much more elegant. I see, is it described somewhe

[sage-devel] Re: addressing notion impedance

On Nov 24, 1:04 pm, "Yegor Bryukhov" <[EMAIL PROTECTED]> wrote: Hi, > > Great!  Welcome!  What sort of library are you thinking of? > > Magnus - a package for finitely presented groups, may be. We have talked to Tim Daly about this and so far nothing has happened in that directory. At least t

[sage-devel] Re: A simpler SAGE?

For security, I just mean that if I have it running on a server, I don't want people to be able to do malicious things like play with the filesystem, send mail, or drop mysql tables. More than a sandbox, however: you shouldn't be able to disable it, or otherwise mess things up so that I have to r

[sage-devel] Re: addressing notion impedance

> Great! Welcome! What sort of library are you thinking of? Magnus - a package for finitely presented groups, may be. > It's a possibility. If there was a library that only worked for sparse > matrices, but the user wanted to use a function on a dense matrix, I > don't see any way around conv

[sage-devel] Re: error in trying to use the numpy cython buffer interface

On Nov 24, 12:31 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > On Nov 24, 2008, at 9:49 AM, mabshoff wrote: > > Robert: Are you working on the updated cython.spkg or is that not on > > your to do list? I am sure in that case somebody else will take care > > of it. > > Cython 0.10.1 wasn't

[sage-devel] Re: error in trying to use the numpy cython buffer interface

On Nov 24, 2008, at 9:49 AM, mabshoff wrote: > On Nov 24, 8:29 am, Jason Grout <[EMAIL PROTECTED]> wrote: >> Jason Grout wrote: > > > >> Can we get this patch (or an equivalent one) into Sage as soon as >> possible? > > I assume we will upgrade to Cython 0.10.1 in Sage 3.2.1, so if Robert > ei

[sage-devel] Re: addressing notion impedance

On Nov 24, 12:19 pm, Jason Grout <[EMAIL PROTECTED]> wrote: > >> Firstly, Sage is based on an object oriented language (Python > >> respectively Cython). > >> For example, having different flavours of matrices (sparse, dense, > >> special implementation over GF(2), defined in various interfac

[sage-devel] Re: addressing notion impedance

Yegor Bryukhov wrote: >> Probably other people have a more substantial answer, but let's try... > > Thank you, Simon, it did bring some light. > I was thinking about this problem not from an end-user point of view > but as a (potential) developer of one of these libraries. Great! Welcome! What

[sage-devel] Re: sage-3.2

On Nov 24, 1:48 am, "Minh Nguyen" <[EMAIL PROTECTED]> wrote: > Hi Michael, Hi Minh, > I re-ran the tests under the above Mac OS X system, using this command: > > /path-to-sage-root/sage -testall -verbose > > This time, I only have one failed test, namely > > sage -t -verbose devel/sage/sage/

[sage-devel] Re: timeit limitations?

Dear Tim, On Nov 24, 8:41 pm, "Tim Lahey" <[EMAIL PROTECTED]> wrote: > var('x') > f = 2*x/sin(x)^2 > f.integrate(x) > axiom.integrate(f,x) > timeit(f.integrate(x)) > timeit(axiom.integrate(f,x)) AFAIK, unlike "time", which is prefixed to an actual command, "timeit" is a function that expects a s

[sage-devel] Re: timeit limitations?

On Mon, Nov 24, 2008 at 2:09 PM, William Stein <[EMAIL PROTECTED]> wrote: > > > Precisely *exactly* how are you using timeit?! Paste in an exact session. > > Also, note that there is timeit('stuff'), which is a function call, and > %timeit stuff > which is an ipython magic command that is "buggy

[sage-devel] Re: timeit limitations?

On Mon, Nov 24, 2008 at 8:29 AM, Tim Lahey <[EMAIL PROTECTED]> wrote: > > Hi, > > In exploring integration using FriCAS vs. Maxima, I've > noticed that timeit doesn't seem to want to work > for integration. Precisely *exactly* how are you using timeit?! Paste in an exact session. Also, note tha

[sage-devel] Re: Vote for ecl/boehmgc and removal of clisp

On Nov 24, 7:19 am, Robert Dodier <[EMAIL PROTECTED]> wrote: > mabshoff wrote: Hi Robert, > > this has been discussed a bunch of time, but now finally the first > > official move: I would like to remove clisp and switch over to ecl as > > the base for Maxima as well as the optional FriCAS spkg

[sage-devel] Re: error in trying to use the numpy cython buffer interface

On Nov 24, 8:29 am, Jason Grout <[EMAIL PROTECTED]> wrote: > Jason Grout wrote: > Can we get this patch (or an equivalent one) into Sage as soon as possible? I assume we will upgrade to Cython 0.10.1 in Sage 3.2.1, so if Robert either (a) releases Cython 0.10.2 or (b) feels comfortable with

[sage-devel] Re: addressing notion impedance

> Probably other people have a more substantial answer, but let's try... Thank you, Simon, it did bring some light. I was thinking about this problem not from an end-user point of view but as a (potential) developer of one of these libraries. > > Firstly, Sage is based on an object oriented lang

[sage-devel] Re: addressing notion impedance

Dear Yegor, On Nov 24, 4:27 pm, "Yegor Bryukhov" <[EMAIL PROTECTED]> wrote: > Ideally, the end user should not be aware of the fact that s/he uses 5 > libraries. > > So, what's Sage's approach to this problem? Probably other people have a more substantial answer, but let's try... Firstly, Sage

[sage-devel] Re: error in trying to use the numpy cython buffer interface

Jason Grout wrote: > I'm just finishing making RDF and CDF vectors use numpy under the hood. > The last problem I'm having is trying to use the Cython buffer > interface in sage/rings/polynomial/real_roots.pyx to access the > underlying numpy array. > FYI, Dag and I corresponded about this

[sage-devel] timeit limitations?

Hi, In exploring integration using FriCAS vs. Maxima, I've noticed that timeit doesn't seem to want to work for integration. Taking an example from the Axiom Wiki, If I do: var('x') f = 2*x/sin(x)^2 f.integrate(x) axiom.integrate(f,x) all is fine. However, as soon as I try to put a timeit arou

[sage-devel] Re: Temporary Mac Launcher Application

On Nov 24, 9:47 am, Jason Grout <[EMAIL PROTECTED]> wrote: > Daniel Stine wrote: > > I hacked together an application for my own personal use that can be > > used as a launcher for Sage, though I decided to share it, since I'm > > quite sure someone will find it useful.  It consists of a bash sh

[sage-devel] Re: trac account name map to real names?

William Stein wrote: > On Sun, Nov 23, 2008 at 2:04 PM, mabshoff <[EMAIL PROTECTED]> wrote: >> We currently have in excess of 150 accounts in the Sage trac, so >> before I go off and do this I wanted to hear what people think. > > Damn! There are a lot of Sage developers. If 150 people have ac

[sage-devel] addressing notion impedance

Hi, I have a general question. Sage incorporates a bunch of mathematical libraries, if it haven't happened yet, it'll happen soon that two libraries operate on same mathematical concepts/objects but they express and represent them differently (trivial example - one library uses data structures ta

[sage-devel] Re: A simpler SAGE?

Jeff Pickhardt wrote: > I'm thinking I'll probably just continue my own back end (which I've > started rewriting in Python) but leverage some hand-picked advanced > functionalities like integration. The advantage of this is that I can > make it secure and easy to use; the disadvantage is that it

[sage-devel] Re: Vote for ecl/boehmgc and removal of clisp

mabshoff wrote: > this has been discussed a bunch of time, but now finally the first > official move: I would like to remove clisp and switch over to ecl as > the base for Maxima as well as the optional FriCAS spkgs. ecl is > faster, builds and works on way more platforms including 32 and 64 bit

[sage-devel] Re: A simpler SAGE?

Jeff Pickhardt wrote: > When I say "simple" I mean really, really, REALLY simple. So simple > it's intuitive for non-programmers. I can program and I could always > run Python scripts or use command line interfaces myself, but I have > friends who want something even easier. My friends are pret

[sage-devel] Re: Temporary Mac Launcher Application

Daniel Stine wrote: > I hacked together an application for my own personal use that can be > used as a launcher for Sage, though I decided to share it, since I'm > quite sure someone will find it useful. It consists of a bash shell > script packaged in a small .app bundle. I'm not as familiar wi

[sage-devel] Re: Vote for ecl/boehmgc and removal of clisp

+1 Hopefully on my bronze age PPC Mac PowerBook, there will be fewer issues with Maxima ... Cheers, gsw On 23 Nov., 21:18, mabshoff <[EMAIL PROTECTED]> wrote: > Hello folks, > > this has been discussed a bunch of time, but now finally the first > official move: I would like to remove clisp and

[sage-devel] Re: sage-3.2

Hi Michael, On Sat, Nov 22, 2008 at 11:57 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Nov 22, 11:54 pm, "Minh Nguyen" <[EMAIL PROTECTED]> wrote: >> On Sat, Nov 22, 2008 at 11:49 PM, mabshoff <[EMAIL PROTECTED]> wrote: >> >> [...] >> >> The source distro built fine on the following 32-bit s

[sage-devel] Re: A simpler SAGE?

On Mon, Nov 24, 2008 at 12:40 AM, Jeff Pickhardt <[EMAIL PROTECTED]> wrote: > When I say "simple" I mean really, really, REALLY simple. So simple > it's intuitive for non-programmers. I can program and I could always > run Python scripts or use command line interfaces myself, but I have > friend