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

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

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

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

Re: [sage-devel] sphinx, texinfo and emacs

I don't understand -- aren't you getting the full documentation, as in this page: http://doc.sagemath.org/html/en/reference/combinat/sage/combinat/posets/__init__.html#sage-combinat-posets At least, on my machine it prints the exact same information. Best, Johan 'Martin R' via sage-devel

Re: [sage-devel] Bug: Affecting a value to an integer

Le 20/10/2016 à 13:15, John Cremona a écrit : That is surely a bug. I always assumed that the only trabformation made when inputting a .sage file whe nit is converted to a .py file was to apply the same preparsing as when you type into the command line. But that is not the case: note that

[sage-devel] Re: sphinx, texinfo and emacs

after patching and doing ./sage -docbuild reference texinfo I get many *.texi files, and in each directory a makefile. After installing makeinfo (sudo apt-get install info), and doing make, I get very nice looking info files, and at least the top one seems to work very well. Even in the

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

It might be allowed but I do not see the point of using it. The most reasonable way is cdef int a # or possibly, unsigned int, size_t, etc for a in range(100): ... And this has to be thought as the C for loop int a; for(a = 0; a < 100; a++) ... And as Volker said, it is always a good

Re: [sage-devel] sphinx, texinfo and emacs

Yes, but there are no links. Or do you have them? (I admit, I made a mistake: the text is the same, contrary what I wrote. Although I'm not sure that showing just the docstring of the class is best possible: I recently used automethod, and this documentation is not shown...) Martin Am

[sage-devel] Re: sphinx, texinfo and emacs

as a first step to answering (2), I just applied the patch below, and it seems to build the reference in texinfo format. diff --git a/src/sage_setup/docbuild/__init__.py b/src/sage_setup/docbuild/__init__.py index 0bd52a6..9ddf7d4 100644 --- a/src/sage_setup/docbuild/__init__.py +++

Re: [sage-devel] Bug: Affecting a value to an integer

That is surely a bug. I always assumed that the only trabformation made when inputting a .sage file whe nit is converted to a .py file was to apply the same preparsing as when you type into the command line. But that is not the case: note that preparse('0 = 42') returns '__tmp__=var("0");

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

xrange will stilll be allowed in cython files, even after (if) we switch to python3 Frederic Le jeudi 20 octobre 2016 11:47:38 UTC+2, Johan S. R. Nielsen a écrit : > > >> sage: a = range(10**8) # takes a lot of memory > >> sage: del a# free the memory > > > > Ok, so now,

Re: [sage-devel] sphinx, texinfo and emacs

> Yes, but there are no links. Or do you have them? True, they are not links. It would be nice if they were, though personally I like that what is printed is the actual module name that I should type in followed by ? to see its doc. That's probably how I would do it even if it was a link, and

Re: [sage-devel] sphinx, texinfo and emacs

Am Donnerstag, 20. Oktober 2016 13:05:59 UTC+2 schrieb Johan S. R. Nielsen: > > > Yes, but there are no links. Or do you have them? > > True, they are not links. It would be nice if they were, though > personally I like that what is printed is the actual module name that I > should type in

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

2016-10-20 00:24:17 UTC+2, Paul Masson: > doc.sagemath.org is now showing up in Google searches, > including the link that initiated this thread. Hoorray! This is great news for all SageMath users. Thanks Paul and Harald for your efforts to make it happen. And thanks to anyone else involved (eg

[sage-devel] trac down?

I can neither see tickets, nor even ssh into the server. Looks like a reboot will be needed. Dima -- 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] trac rebooted, seems OK now

see the subject -- 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

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

> In case no one else has noticed, doc.sagemath.org is now showing up in > Google searches, including the link that initiated this thread. Indeed I have noticed! It's really good news for us and - especially - for new Sage users :-) Best, Johan Paul Masson writes: > In case no one else has

Re: [sage-devel] Bug: Affecting a value to an integer

> 0 = 42 > print 0 Hahaha, easiest way to get a contradiction and thereby prove any statement in Sage :-D -- 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] sphinx, texinfo and emacs

As you may know, using https://github.com/sagemath/sage-shell-mode, working with sage in emacs is a very enjoyable pastime. In particular, typing at the sage prompt sage: sage.combinat.posets? opens a new frame and displays the documentation of sage.combinat.posets there. However, to my

[sage-devel] Bug: Affecting a value to an integer

Consider the following code: 0 = 42 print 0 If you write it into sage's ipython, it of course gives you an error. More precisely, you get ValueError: The name "0" is not a valid Python identifier. But suppose you write it into a file bug.sage, and execute it using sage bug.sage, you get 42!

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

>> sage: a = range(10**8) # takes a lot of memory >> sage: del a# free the memory > > Ok, so now, I understand why it takes the memory: a list was created. Using xrange instead of range will also avoid creating the list even without cdef'ing a (the code is still slow of

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

On Thursday, October 20, 2016 at 8:42:05 AM UTC+2, vdelecroix wrote: > 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 Ok, so now, I

Re: [sage-devel] sage 7.4 does not build on Ubuntu 16.10

In deed, the GCC hardening in Ubuntu 16.10 is responsible for the make error. Two questions: 1. How can I configure make to circumvent the error in building flint? 2. Are some other sage packages affected by GCC hardening? Herbert Am Donnerstag, 20. Oktober 2016 14:40:13 UTC+2 schrieb

Re: [sage-devel] Re: ordering of polynomials and failing optional doctest for database_jones_numfield

apparently not so many people care for the patchbot's results.. and optional packages are probably not tested by Volker Le jeudi 20 octobre 2016 19:06:03 UTC+2, vdelecroix a écrit : > > Thanks for your answer. > > Why was it not a blocker!? I would have thought that passing all tests >

Re: [sage-devel] Re: ordering of polynomials and failing optional doctest for database_jones_numfield

Thanks for your answer. Why was it not a blocker!? I would have thought that passing all tests (including optional) was a prerequisite for a stable Sage release... Vincent -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] ordering of polynomials and failing optional doctest for database_jones_numfield

Hello, Some tests related to the optional package database_jones_numfield fail for some ordering reason [1]. Sadly this is broken in the new Sage release. It is probably related to some changes in the ordering of polynomials. Does anybody have an idea when it started? What might be the cause?

[sage-devel] Re: ordering of polynomials and failing optional doctest for database_jones_numfield

there is already a positive reviewed ticket for this issue Frederic Le jeudi 20 octobre 2016 18:48:03 UTC+2, vdelecroix a écrit : > > Hello, > > Some tests related to the optional package database_jones_numfield > fail for some ordering reason [1]. Sadly this is broken in the new > Sage

Re: [sage-devel] Re: ordering of polynomials and failing optional doctest for database_jones_numfield

I do not agree with you Frédéric. Many reviewers care about patchbot results! However, it would be better to have something dedicated to Sage releases. For example we could have special tests on each release candidate. A release candidate could well be linked to a trac ticket with an attached

Re: [sage-devel] LAPACK from sage (i. e. usable in sage -sh) ?

libopenblas.so to liblapack.so? Yes it should and I think we even should do it in spkg-install. Feel free to open a ticket. François > On 21/10/2016, at 10:23, Emmanuel Charpentier > wrote: > > Would it be sufficient to link libosympenblas.so to liblapack.so in

Re: [sage-devel] LAPACK from sage (i. e. usable in sage -sh) ?

This is because automatic blas/lapack detection is a hopeless task. You should pass your lapack libraries to the configuration script. If you can’t, hack it. And now that we have switched to openblas, -lopenblas provides lapack. François > On 21/10/2016, at 10:04, Emmanuel Charpentier

Re: [sage-devel] LAPACK from sage (i. e. usable in sage -sh) ?

Would it be sufficient to link libosympenblas.so to liblapack.so in $SAGE_ROOT/local/lib/ ? Thanks for the hint ! -- Emmanuel Charpentier Le jeudi 20 octobre 2016 23:12:43 UTC+2, François a écrit : > > This is because automatic blas/lapack detection is a hopeless task. > You should pass your

[sage-devel] LAPACK from sage (i. e. usable in sage -sh) ?

Something just changed in the Sage build process : as of 7.4, LAPACK is no longer available to programs running in the Sage shell. Case in point : I want to install JAGS (an MCMC sampler), which is needed by the rjags R package, of some use to Bayesian R users... This package compiled fine in

Re: [sage-devel] LAPACK from sage (i. e. usable in sage -sh) ?

I tried it, and it works for me (superficial test : jags compiles, the R packages using install, a,d an old R script runs). This is now Trac#21736 . I won't do it immediately (my "woking Sage installation is somewhat patched, and going back to

Re: [sage-devel] LAPACK from sage (i. e. usable in sage -sh) ?

I agree it would be best. Unfortunately it may not always be possible to do that without heavy hacking. Adding the liblapack link has trade-off, it would make some stuff work out of the box but it could also hide problems on the long term. Really upstream of any project using blas/lapack needs to

Re: [sage-devel] LAPACK from sage (i. e. usable in sage -sh) ?

We do have a pc file so IMHO the best way is to rely on the output of $ pkg-config --cflags lapack -I/mnt/disk/home/release/Sage/local/include $ pkg-config --libs lapack -L/mnt/disk/home/release/Sage/local/lib -lopenblas On Thursday, October 20, 2016 at 11:12:43 PM UTC+2, François wrote: > >

[sage-devel] Re: line_profiler (%lprun) also broken from IPython upgrade

This was a known bug in line_profiler that is fixed with the 2.0 release. Try upgrading to line_profiler==2.0 and let us know if there's still a problem. On Thursday, September 1, 2016 at 7:03:31 AM UTC-7, Travis Scrimshaw wrote: > > I just installed the line profiler because I want to do

Re: [sage-devel] Notebook stuck on "N?" with a worksheet

On Friday, October 7, 2016 at 5:32:24 AM UTC-4, Jori Mäntysalo wrote: > > On Fri, 7 Oct 2016, Jori Mäntysalo wrote: > > > Could someone try SageNB with http://www.sis.uta.fi/~jm58660/Broken.sws > > More about this: the computation works, but getting output back to the > browser window does

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

Searching for Sage on Google was hit-and-miss for me yesterday but much more consistent today. It apparently takes time for all Google servers to sync their search results and may take a couple more days to appear consistently. On Thursday, October 20, 2016 at 6:36:07 PM UTC-7, kcrisman wrote:

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

On Wednesday, October 19, 2016 at 6:24:17 PM UTC-4, Paul Masson wrote: > > 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. > >> >> Boy, I sure hope you are

[sage-devel] Re: line_profiler (%lprun) also broken from IPython upgrade

On Thursday, October 20, 2016 at 5:06:58 PM UTC-5, Brett Olsen wrote: > > This was a known bug in line_profiler that is fixed with the 2.0 release. > Try upgrading to line_profiler==2.0 and let us know if there's still a > problem. > > Yes, upgrading fixed it. Thank you! Best, Travis --

[sage-devel] Re: sphinx, texinfo and emacs

this is now https://trac.sagemath.org/ticket/21734 help is much appreciated -- 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

Re: [sage-devel] sage 7.4 does not build on Ubuntu 16.10

The problem seems to be that your GCC was configured with --enable-default-pie and FLINT does not like that. More information at https://wiki.ubuntu.com/SecurityTeam/PIE -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

[sage-devel] sage 7.4 does not build on Ubuntu 16.10

Link problem in flint-2-5.2: /usr/bin/ld: -r and -pie may not be used together Log enclosed. -- 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