Hi Jean-Pierre, On 2012-12-31, Jean-Pierre Flori <jpfl...@gmail.com> wrote: >> What you see is that during >> our callback, a garbage collection is triggered! This of course >> discovers all sorts of things that can be deleted, including things >> that are already scheduled for deletion. Other interpretations would >> be very welcome. >> > It seems very plausible, whence the possible need to look at Py_Clear. > > The difference between the "del A[1]" and "A.__delitem__(1)" might only be > the fact that in the latter case (where more fucntions calls are performed) > a gc is triggered whereas its not in the first case, that's just a wild > guess though.
That could be it. A garbage collection can (IIRC) occur at any function call. I was not aware that "del A[1]" would avoid that function call. And of course, if a garbage collection occurs while one attempts to remove something that was scheduled for deletion on a previous collection, it seems messy. Question: Where should this bug fix occur? Shall I open a separate ticket next year? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
