Re: [sage-devel] droste effect in Sage

2010-03-14 Thread William Stein
2010/3/14 Rado : > Hello, > > I have the following simple http://www.math.uiuc.edu/~rkirov2/files/escher.py > code in pure Python (using the python image library) that produces > Droste effect pictures like this one > http://www.math.uiuc.edu/~rkirov2/files/spiral.jpg > . I wrote the code over 2 y

Re: syntax support for _sig_on / _sig_off in cython (Re: [sage-devel] Re: Memory leak)

2010-03-14 Thread Gonzalo Tornaria
On Sun, Mar 14, 2010 at 9:21 PM, Brian Granger wrote: > Gonzalo, > Thanks for starting this discussion.  I am willing to help with this effort > as I definitely need this capability.  Part of the challenge will be > figuring out how to do this on Windows. Not necessarily. I think signals(2) is pa

Re: syntax support for _sig_on / _sig_off in cython (Re: [sage-devel] Re: Memory leak)

2010-03-14 Thread Gonzalo Tornaria
On Sat, Mar 13, 2010 at 7:22 PM, Robert Bradshaw wrote: > On Mar 13, 2010, at 4:04 PM, Gonzalo Tornaria wrote: >> What are the options for supporting this (either the >> decorator/function attribute or the with-clause)? > > We can support both. We could support custom signal handlers via something

Re: syntax support for _sig_on / _sig_off in cython (Re: [sage-devel] Re: Memory leak)

2010-03-14 Thread Brian Granger
> no_signals? signals_disabled? This would give something like: > >with no_signals: >... > >with signals_disabled: >... > > The current names in Sage of _sig_on/_sig_off are a bit confusing and the names no_signals or signals_disabled carry forward that confu

Re: syntax support for _sig_on / _sig_off in cython (Re: [sage-devel] Re: Memory leak)

2010-03-14 Thread Brian Granger
Gonzalo, Thanks for starting this discussion. I am willing to help with this effort as I definitely need this capability. Part of the challenge will be figuring out how to do this on Windows. Eventually, I think we do want to capability to be built into Cython. But, while we experiment with di

[sage-devel] Re: Logistic Curve Fitting in Sage

2010-03-14 Thread Alec Mihailovs
On Mar 12, 4:22 am, Joal Heagney wrote: > Hi guys and gals, > Currently I'm attempting to fit the following data to the general > logistic model: > > [(0,0),(1,0),(2,13),(3,28),(4,48),(5,89),(6,107),(7,168),(8,188),(9,209)] > > The form of the logistic curve I am using is: > > K/(1 + a*exp(r * (t

Re: [sage-devel] Open MPI - Sage version is ancient.

2010-03-14 Thread Dr. David Kirkby
William Stein wrote: On Sun, Mar 14, 2010 at 4:38 PM, Dr. David Kirkby 1) I closed your ticket as a dup of http://trac.sagemath.org/sage_trac/ticket/8455 #8455 is to update MPIR, not Open MPI. Woops -- this is what i get for checking email during a talk. I'll let you off! Mike Hanson ha

[sage-devel] droste effect in Sage

2010-03-14 Thread Rado
Hello, I have the following simple http://www.math.uiuc.edu/~rkirov2/files/escher.py code in pure Python (using the python image library) that produces Droste effect pictures like this one http://www.math.uiuc.edu/~rkirov2/files/spiral.jpg . I wrote the code over 2 years ago in java. Recently, I

Re: [sage-devel] Open MPI - Sage version is ancient.

2010-03-14 Thread William Stein
On Sun, Mar 14, 2010 at 4:38 PM, Dr. David Kirkby wrote: > William Stein wrote: >> >> On Sun, Mar 14, 2010 at 2:56 PM, Dr. David Kirkby >> wrote: >>> >>> I tried to build the optional Open MPI package (version 1.1.4) on Solaris >>> and it fails. The version in Sage is 1.1.4, which was released on

Re: [sage-devel] Open MPI - Sage version is ancient.

2010-03-14 Thread Dr. David Kirkby
William Stein wrote: On Sun, Mar 14, 2010 at 2:56 PM, Dr. David Kirkby wrote: I tried to build the optional Open MPI package (version 1.1.4) on Solaris and it fails. The version in Sage is 1.1.4, which was released on Jan 30, 2007, so is more than 3 years old. The optional package is very diff

Re: [sage-devel] Open MPI - Sage version is ancient.

2010-03-14 Thread William Stein
On Sun, Mar 14, 2010 at 2:56 PM, Dr. David Kirkby wrote: > I tried to build the optional Open MPI package (version 1.1.4) on Solaris > and it fails. The version in Sage is 1.1.4, which was released on Jan 30, > 2007, so is more than 3 years old. > > The optional package is very different to most o

[sage-devel] tick labels and coding a plot semilogx

2010-03-14 Thread Scott
I am trying to code loglog and semilog plot tools, however I cannot find the place to manipulate the ticklabels. sage.plot.list_plot is my template. Where are the tick labels set in list_plot? I want to change the tick labels from [1 ,2,3] to [1e1,1e2,1e3] without altering the plot. Cheers Sco

Re: [sage-devel] Success / Failures of 'optional' packages on Solaris.

2010-03-14 Thread Dr. David Kirkby
Dr. David Kirkby wrote: I tried to install some optional packages and immediately hit a snag due to a GNUism, where 'grep' is called with the '-o' option. John Palmieri thought the -o was unneeded, and that is indeed the case. If someone wants to review that patch (only removal of two character

[sage-devel] Open MPI - Sage version is ancient.

2010-03-14 Thread Dr. David Kirkby
I tried to build the optional Open MPI package (version 1.1.4) on Solaris and it fails. The version in Sage is 1.1.4, which was released on Jan 30, 2007, so is more than 3 years old. The optional package is very different to most other spkg files. * No SPKG.txt * No Mercurial repository * S

[sage-devel] Re: GSoC 2010 project idea: adding functionality to PYCA

2010-03-14 Thread Kazuo Thow
On Mar 13, 6:14 pm, Dan Drake wrote > That sounds like a nice project, and I think it's a good idea. My > impression, however, is that the SoC selection committee doesn't like > projects that come across as "too mathy". I've been hearing the same from other people; currently I'm looking into alte

Re: syntax support for _sig_on / _sig_off in cython (Re: [sage-devel] Re: Memory leak)

2010-03-14 Thread Nicolas M. Thiery
On Sat, Mar 13, 2010 at 04:22:09PM -0800, Robert Bradshaw wrote: > There's also the question of naming--sig_on probably isn't the > clearest name. no_signals? signals_disabled? This would give something like: with no_signals: ... with signals_disabled: ...

Re: [sage-devel] Re: expunging SAGE

2010-03-14 Thread John Cremona
On 14 March 2010 19:15, John H Palmieri wrote: > On Mar 14, 11:04 am, John Cremona wrote: >> When quitting Sage from the command line one sees something like this: >> >> Exiting SAGE (CPU time 0m0.04s, Wall time 0m0.63s). >> >> Note "SAGE" and not "Sage".  I went through and changed the small >>

[sage-devel] Re: expunging SAGE

2010-03-14 Thread John H Palmieri
On Mar 14, 11:04 am, John Cremona wrote: > When quitting Sage from the command line one sees something like this: > > Exiting SAGE (CPU time 0m0.04s, Wall time 0m0.63s). > > Note "SAGE" and not "Sage".  I went through and changed the small > number of places where "SAGE" is ever output.  (I skippe

[sage-devel] expunging SAGE

2010-03-14 Thread John Cremona
When quitting Sage from the command line one sees something like this: Exiting SAGE (CPU time 0m0.04s, Wall time 0m0.63s). Note "SAGE" and not "Sage". I went through and changed the small number of places where "SAGE" is ever output. (I skipped comments, of which there are a lot, and obviously

Re: [debian-sage] Re: [sage-devel] Re: Debian package...

2010-03-14 Thread William Stein
On Sat, Mar 13, 2010 at 6:48 PM, Tim Abbott wrote: > On Sun, 14 Mar 2010, Alex Ghitza wrote: > >> > However, they did say that given the circumstances, it might be possible >> > to push through a major update to the package to Karmic when once one is >> > available. >> > >> > So I think this leave

[sage-devel] Re: Mathematica doctest

2010-03-14 Thread Felix Lawrence
I've put a patch up for http://trac.sagemath.org/sage_trac/ticket/8495 that fixes the regressions while keeping the new functionality: sage -t -optional "devel/sage/sage/interfaces/mathematica.py" [7.0 s] -- All tests pa

Re: [sage-devel] Re: Debian package...

2010-03-14 Thread Kasper Peeters
> That review process is what killed the Debian sagemath package > -- Upgrading during the review process > sends you to the back of the queue, and by a year after my original > submission, I had left MIT graduate school to start a startup, and I no > longer had the time to upgrade past a year of S