For the python-level leak, I think it's down to this:
x = polygen(ZZ)
v = x # or 1/3 or RR(3) but not, say 3
pre={id(c) for c in gc.get_objects()}
for _ in range(20000): test =
sage.rings.polynomial.polynomial_element.Polynomial.__call__(x,v)
It ends up letting a lot of 1-element tuples of the form (v,) lie around.
Note that the call in question is an unbound method call,
(in the original example, where there was a number field element
comparison, things do boil down to polynomial evaluation in
sage.rings.number_field.number_field_element.NumberFieldElement._richcmp_
), which is a relatively unusual thing to do, so there might be room there
for a cython error, but then it's strange that the problem does not occur
when v is an integer.
--
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@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
