[sage-devel] Re: cython memory leak when one's forget to cdef the for loop variable

2016-10-19 Thread Volker Braun
On Thursday, October 20, 2016 at 1:19:51 AM UTC+2, Sébastien Labbé wrote: > > Does this also explain the leak? > Freed memory is not immediately returned to the system (mostly because it would be hilariously slow for small allocations). Whether a one-off computation increases process memory usag

Re: [sage-devel] Re: cython memory leak when one's forget to cdef the for loop variable

2016-10-19 Thread Vincent Delecroix
It might not be a leak. *After* the loop the memory should be back to normal. The very same as with sage: a = range(10**8) # takes a lot of memory sage: del a# free the memory Vincent PS: This would have been different with Python 3. -- You received this message because yo

[sage-devel] Re: cython memory leak when one's forget to cdef the for loop variable

2016-10-19 Thread Sébastien Labbé
Does this also explain the leak? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage

[sage-devel] Re: cython memory leak when one's forget to cdef the for loop variable

2016-10-19 Thread Volker Braun
PS: Write your code in a file and compile it with "cython -a myfile.pyx", that generates a html file with explanations. On Thursday, October 20, 2016 at 1:11:14 AM UTC+2, Volker Braun wrote: > > Thats the expected behavoir. Without type annotation, cython just does the > same as Python (creat

[sage-devel] Re: cython memory leak when one's forget to cdef the for loop variable

2016-10-19 Thread Volker Braun
Thats the expected behavoir. Without type annotation, cython just does the same as Python (create a list of 10**8 elements and iterate over). With type annotation it is a C-level for loop. On Thursday, October 20, 2016 at 12:33:47 AM UTC+2, Sébastien Labbé wrote: > > Dear sage-devel, > > Writin

[sage-devel] cython memory leak when one's forget to cdef the for loop variable

2016-10-19 Thread Sébastien Labbé
Dear sage-devel, Writing cython code, I was having a problem with memory leaks, and I managed to simplify the problem to a simple for loop computing a sum. If the loop variable a is cdef, everything is fine: sage: %%cython : def test_with_cdef_a(int N): : cdef long S = 0 : c

[sage-devel] Re: doc.sagemath.org gone from google

2016-10-19 Thread Paul Masson
In case no one else has noticed, doc.sagemath.org is now showing up in Google searches, including the link that initiated this thread. Google taketh away, and Google giveth back. On Sunday, August 7, 2016 at 8:25:56 AM UTC-7, William wrote: > > I'm googling for links to the sage reference manua

Re: [sage-devel] NTL 1v0.1.0

2016-10-19 Thread François Bissey
On 19/10/16 23:57, Victor Shoup wrote: Sure. Will do. For people not on libsingular-devel, Hannes' answer: == The problem is a fast/convinient conversion between long integers in factory of type CanonicalForm (which is in principle a mpz_t number) and long integers in NTL of type ZZ (wh

Re: [sage-devel] Re: Is Brown's construction available in the graph component of sagemath?

2016-10-19 Thread Dima Pasechnik
On Wednesday, October 19, 2016 at 7:05:23 AM UTC+1, ywr nn wrote: > > hi, Dima! > > In my context, for every power of primes q, Brown's construction gives a > graph with order q^2+q+1, maximum degree q+1, diameter 2. > The graph is not a regular one. The degree sequence of the graph is > [(q+1)

[sage-devel] Re: Embedding graphs on the projective plane

2016-10-19 Thread Dima Pasechnik
On Tuesday, October 18, 2016 at 6:59:09 PM UTC+1, Joshua Fallon wrote: > > Hi all, Sage rookie here. I've been working on writing functions to test > whether a graph can be embedded on the projective plane, as in Myrvold and > Roth's paper ( > http://citeseerx.ist.psu.edu/viewdoc/download?doi=1

Re: [sage-devel] 7.4 release: please don't have fpylll build-depend on Sage

2016-10-19 Thread Ximin Luo
Thanks a lot! 'Martin R. Albrecht' via sage-devel: > Hi all, > > this is now https://trac.sagemath.org/ticket/21728 > > Cheers, > Martin > -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git -- You received this message because you are su

Re: [sage-devel] 7.4 release: please don't have fpylll build-depend on Sage

2016-10-19 Thread Ximin Luo
Jeroen Demeyer: > On 2016-10-18 17:52, Ximin Luo wrote: >> (2) In the long run, one can think about splitting out sage.rings.integers >> (and related things) into a small library "sage-types" or something like >> that. Then sagelib and fpylll can depend on this, and there would be no >> circular

Re: [sage-devel] NTL 1v0.1.0

2016-10-19 Thread Victor Shoup
Sure. Will do. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroup

Re: [sage-devel] 7.4 release: please don't have fpylll build-depend on Sage

2016-10-19 Thread Francois Bissey
Very much appreciated Martin! Since this ticket doesn’t touch sagelib Gentoo, Debian and other distributions will be able to use fpylll-0.23 directly in sage-7.4. I’ll issue a revision of the sage-7.4 ebuild tomorrow and review the ticket if no one has done it by then. François > On 19/10/2016,

Re: [sage-devel] 7.4 release: please don't have fpylll build-depend on Sage

2016-10-19 Thread 'Martin R. Albrecht' via sage-devel
Hi all, this is now https://trac.sagemath.org/ticket/21728 Cheers, Martin Martin R. Albrecht writes: > Hi there, > > Ximin Luo writes: >> We can do "pre-install tests" with Sage 7.3, by doing a "dummy >> install" using Sage's Makefiles, running the tests here, then >> installing them to the "re

Re: [sage-devel] 7.4 release: please don't have fpylll build-depend on Sage

2016-10-19 Thread Jeroen Demeyer
On 2016-10-18 17:52, Ximin Luo wrote: (2) In the long run, one can think about splitting out sage.rings.integers (and related things) into a small library "sage-types" or something like that. Then sagelib and fpylll can depend on this, and there would be no circular dependency, even when Debia