Hi Peter, On 2014-11-11, Peter Mueller <ypf...@googlemail.com> wrote: > A tentative solution seems to be to put a `collect()' inside the loop (and > a `from gc import collect' at the beginning of the program). Still, I > believe that this issue deserves attention.
If gc.collect() solves the issue, then I suppose it is not a memory leak after all. Unless you explicitly disable it, Python cyclic garbage collector will occasionally do a collection anyway (though not after each deletion of an object). Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
