[sage-devel] Wrong symbolic sum

sage: (n,k,j)=var('n,k,j') sage: sum(binomial(n,k)*binomial(k-1,j)*(-1)**(k-1-j),k,j+1,n) 0 sage: (n,j)=(5,3) sage: sum(binomial(n,k)*binomial(k-1,j)*(-1)**(k-1-j) for k in range(j +1,n+1)) 1 The symbolic sum being 0 is only trivially valid for nhttp://groups.google.com/group/sage-devel URL: http:

[sage-devel] Re: new keywords for limit()

Hi Burcin, > Here is the help page for the MMA command Limit: > > http://reference.wolfram.com/mathematica/ref/Limit.html > > They seem to only allow -1 and 1 for the Direction argument. Yes, I looked at that later. Notice that http://reference.wolfram.com/mathematica/tutorial/FindingLimits.htm

Re: [sage-devel] Re: can't -sdist a -bdist copy of Sage

On Mon, 26 Jul 2010 at 10:45AM -0700, William Stein wrote: > > So "sage -sdist" should check to see if SAGE_ROOT/spkg/standard/ > > atlas... is above a certain size, and if not, print a warning about > > copying real spkg's and/or refuse to run? > > Yes. It should do that for all the spkg's though

[sage-devel] Re: [sage-combinat-devel] Python, Sage, categories

On Mon, Jul 26, 2010 at 03:45:29PM -0700, William Stein wrote: > > I'm very sorry to have unfairly bashed the sage-combinat community, and I'm > glad you've jumped to their defense to clarify matters. I was exhausted > after > a very long, sleepless coding sprint (days and days) trying to speed

[sage-devel] Re: [sage-combinat-devel] Python, Sage, categories

On Mon, Jul 26, 2010 at 3:36 PM, Nicolas M. Thiery wrote: >        William, > > >  There is a strong technical issue that needs to be resolved, and for >  which I explicitly take the blame. And I understand your frustration >  when fighting with zillions of technical points. However I perceived >

[sage-devel] Re: [sage-combinat-devel] Python, Sage, categories

William, There is a strong technical issue that needs to be resolved, and for which I explicitly take the blame. And I understand your frustration when fighting with zillions of technical points. However I perceived your e-mail as unfairly bashing the sage-combinat community, whic

Re: [sage-devel] Under what conditions is Cython generating C++ code?

On 2010-Jul-25 02:06:11 -0700, Simon King wrote: >I thought that Cython generates C code, which is then processed >further with gcc. But in this case, it seems that C++ code is >generated. However, this C++ code is still processed with gcc, not g++. This is allowable. gcc and g++ are a front-end

[sage-devel] Re: #9456 I made a mistake - can someone check I've corrected it ok

On Jul 26, 10:22 am, John H Palmieri wrote: > On Jul 26, 7:12 am, Dan Drake wrote: > > > On Mon, 26 Jul 2010 at 11:29AM +0100, Dr. David Kirkby wrote: > > > I managed to overwrite the deps and deps.diff files on #9456 by mistake. > > > Sorry, > > > > I believe I have put them back as they should

Re: [sage-devel] Re: Cython and #define

On 2010-Jul-26 02:52:50 -0700, Simon King wrote: >Hi! > >On 26 Jul., 11:09, Jeroen Demeyer wrote: >> More concretely: in the pari source file src/headers/parigen.h, there is >> #define lgefint(x)      ((long)(((ulong*)(x))[1] & LGBITS)) >> >> But in Sage, in sage/libs/pari/decl.pxi, there is >>  

Re: [sage-devel] Python, Sage, categories

On Fri, Jul 23, 2010 at 1:05 PM, William Stein wrote: > Hi, > > During the last few weeks I've spent time optimizing code, among other > things.  A surprising number of random things I look at in Sage are > too slow by a factor of 10-100, > usually due to programming style.    One way to help to r

[sage-devel] Re: [sage-combinat-devel] Python, Sage, categories

On Fri, Jul 23, 2010 at 01:05:00PM -0700, William Stein wrote: > During the last few weeks I've spent time optimizing code, among > other things. Great! > A surprising number of random things I look at in Sage are too slow > by a factor of 10-100, usually due to programming style. One way to > h

[sage-devel] Re: Some patches in the GIT repository

On Mon, Jul 26, 2010 at 11:02 AM, Bill Allombert wrote: > Dear PARI developers, > > I would like to anounce some patches that are available through the GIT > browser: > > > 1) bill-pari_err_to_GEN > This patch adds a functio

Re: [sage-devel] Re: can't -sdist a -bdist copy of Sage

On Mon, Jul 26, 2010 at 10:24 AM, John H Palmieri wrote: > On Jul 26, 5:08 am, William Stein wrote: >> On Monday, July 26, 2010, Robert Miller wrote: >> > On Mon, Jul 26, 2010 at 6:21 AM, William Stein wrote: >> >> Sdist should 100% work from a binary.  That it doesn't now is a bug. >> >> This

Re: [sage-devel] Re: Cython and #define

On Mon, Jul 26, 2010 at 2:52 AM, Simon King wrote: > Nonetheless, Cython needs to know what argument type and type of > output to expect. Therefore, one has "long lgefint(GEN x)" in the > Cython header. > > It works (at least for me). I admit that it somehow looks wrong, and > indeed it results in

[sage-devel] Re: can't -sdist a -bdist copy of Sage

On Jul 26, 5:08 am, William Stein wrote: > On Monday, July 26, 2010, Robert Miller wrote: > > On Mon, Jul 26, 2010 at 6:21 AM, William Stein wrote: > >> Sdist should 100% work from a binary.  That it doesn't now is a bug. > >> This used to work - I remember doing sage releases myself starting >

[sage-devel] Re: #9456 I made a mistake - can someone check I've corrected it ok

On Jul 26, 7:12 am, Dan Drake wrote: > On Mon, 26 Jul 2010 at 11:29AM +0100, Dr. David Kirkby wrote: > > I managed to overwrite the deps and deps.diff files on #9456 by mistake. > > Sorry, > > > I believe I have put them back as they should be, but could the > > release managers and/or John check

[sage-devel] New Networkx spkg

...and the md5sum for the patch Ben -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sag

Re: [sage-devel] #9456 I made a mistake - can someone check I've corrected it ok

On Mon, Jul 26, 2010 at 3:24 PM, Dr. David Kirkby wrote: > I wish there was a central server where one just checked out the latest > version of deps, then committed it back once once a ticket got positive > review. That could save a lot of this hassle, with endless tickets making > small but signi

Re: [sage-devel] #9456 I made a mistake - can someone check I've corrected it ok

On 07/26/10 03:12 PM, Dan Drake wrote: On Mon, 26 Jul 2010 at 11:29AM +0100, Dr. David Kirkby wrote: I managed to overwrite the deps and deps.diff files on #9456 by mistake. Sorry, I believe I have put them back as they should be, but could the release managers and/or John check this. Johns cha

Re: [sage-devel] #9456 I made a mistake - can someone check I've corrected it ok

On Mon, 26 Jul 2010 at 11:29AM +0100, Dr. David Kirkby wrote: > I managed to overwrite the deps and deps.diff files on #9456 by mistake. > Sorry, > > I believe I have put them back as they should be, but could the > release managers and/or John check this. Johns change was basically: > > -$(INST

Re: [sage-devel] can't -sdist a -bdist copy of Sage

On Monday, July 26, 2010, Robert Miller wrote: > On Mon, Jul 26, 2010 at 6:21 AM, William Stein wrote: >> Sdist should 100% work from a binary.  That it doesn't now is a bug. >> This used to work - I remember doing sage releases myself starting >> from a binary. > > I thought binaries only includ

[sage-devel] ALGLIB spkg is released (second version)

Hello! Second beta of ALGLIB.spkg is ready. It can be downloaded from http://www.alglib.net/share/2010-07-26-alglib-for-sage/ Following issues were solved in this release: * compilation on SPARC/Solaris * missing support for SAGE64 * trashing of SAGE_LOCAL with additional dirs Issues tha

[sage-devel] #9456 I made a mistake - can someone check I've corrected it ok

John Palmieri wrote a blocker ticket #9456 for sage-4.5.2 as libpng was failing to build as zlib was not built. His patch has been merged into sage-4.5.2.alpha1 I managed to overwrite the deps and deps.diff files on #9456 by mistake. Sorry, I believe I have put them back as they should be, but

[sage-devel] Re: Cython and #define

PS: On 26 Jul., 11:52, Simon King wrote: > To my understanding, it is the correct way. That said, working at #9583, the impression came accross that "#define Kstd1_mu mu" in some Singular header resulted in a segfault on t2 when Kstd1_mu was used in some Cython file. But if I understood correctl

[sage-devel] Re: Cython and #define

Hi! On 26 Jul., 11:09, Jeroen Demeyer wrote: > More concretely: in the pari source file src/headers/parigen.h, there is > #define lgefint(x)      ((long)(((ulong*)(x))[1] & LGBITS)) > > But in Sage, in sage/libs/pari/decl.pxi, there is >     long    lgefint(GEN x) To my understanding, it is the

[sage-devel] Cython and #define

Hello, This question is motivated by #9343, but I think it fits here. Suppose I have an external spkg written in C using a lot of #define's. How do I get these #define's to work in Cython? More concretely: in the pari source file src/headers/parigen.h, there is #define lgefint(x) ((long)(((u

Re: [sage-devel] can't -sdist a -bdist copy of Sage

On Mon, Jul 26, 2010 at 6:21 AM, William Stein wrote: > Sdist should 100% work from a binary.  That it doesn't now is a bug. > This used to work - I remember doing sage releases myself starting > from a binary. I thought binaries only included place holders for the spkg's? -- Robert L. Miller

Re: [sage-devel] Re: new keywords for limit()

Hi Rob, On Sat, 24 Jul 2010 22:00:12 -0700 (PDT) Rob Beezer wrote: > Hi Burcin, > > As Dana Ernst has now mentioned on the ticket, this an outgrowth of > the professional development workshop that Jason Grout, Karl-Dieter > Crisman and myself have been running this summer on Sage through the >